[tracker/wip/carlosg/faq: 2/2] website: Add FAQ about versions supported by Tracker

[Carlos Garnacho <carlosg src gnome org>]

commit 1f02eb0e84bc673c299fe3840baf623e77d57dc9
Author: Carlos Garnacho <carlosg gnome org>
Date:   Wed Feb 23 11:18:31 2022 +0100

    website: Add FAQ about versions supported by Tracker
    
    Rationalize why we only support the last stable, and everything
    else is deemed to crash and burn.

 docs/website/faq.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
---
diff --git a/docs/website/faq.md b/docs/website/faq.md
index 9decfefae..2c1a92260 100644
--- a/docs/website/faq.md
+++ b/docs/website/faq.md
@@ -145,3 +145,34 @@ program to run these commands.
 
 [Why does Tracker consume resources on my PC?]: #why-does-tracker-consume-resources-on-my-pc
 [control what Tracker indexes]: #how-can-i-control-what-tracker-indexes
+
+## Which versions of Tracker are supported upstream?
+
+Tracker developers only support the latest stable branch (Note: Tracker uses
+[Semantic versioning](https://semver.org/)), and advises all users and
+distributors to update to it. The behavior of older stable releases staying
+correct and stable can not be guaranteed.
+
+There are two main reasons for this:
+
+  * The seccomp jail set up in `tracker-extract-3` will catch non-observed syscalls
+    and make the process quit. However updates in any of the dependencies used for
+    metadata extraction (or any of their subdependencies) may introduce the usage
+    of different syscalls that might not be observed by the seccomp jail.
+
+    This may happen between micro release updates, or due to different compilation
+    flags.
+
+  * SQLite has a history of API/ABI breaks and other regressions. This may sound
+    anecdotal and unlikely, but Tracker uses SQLite API and logic much more
+    extensively than most other users, there is a close to 100% chance that these
+    will affect Tracker in some way.
+
+    This most often happens between major releases, but distributors also do have
+    a history to push these major version updates to stable/LTS distributions.
+
+The implications of both is the same, handling those situations do not just
+require incessant updates, but also require active attention. Tracker maintainers
+backport these fixes on a best effort basis, but do not have the bandwidth to
+test all combinations induced by different distributions/versions across
+multiple Tracker branches.