diff options
| author | Carlos Garnacho <carlosg@gnome.org> | 2022-02-23 11:18:31 +0100 |
|---|---|---|
| committer | Carlos Garnacho <carlosg@gnome.org> | 2022-02-23 14:09:51 +0100 |
| commit | 368aa4499a01a5b18841e7a626acc20a82e5b8da (patch) | |
| tree | 5d11a378f1de2249dca3d204a67b20eeb05fe73d /docs | |
| parent | 56cb0b81d2a0d18843d92e1e7ba337463293c866 (diff) | |
| download | tracker-368aa4499a01a5b18841e7a626acc20a82e5b8da.tar.gz | |
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.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/website/faq.md | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/docs/website/faq.md b/docs/website/faq.md index 9decfefae..1ab86b2aa 100644 --- a/docs/website/faq.md +++ b/docs/website/faq.md @@ -145,3 +145,33 @@ 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 advise all users and distributors to use the latest stable +release of Tracker. The behavior of older stable releases staying correct and +stable can not be guaranteed, thus they become unsupported. + +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. |