We announce the new LTS (N.10.x) once N+1.0 is released. Rationale:
We need to have feedback on a release before it can be considered super stable and thus we usually need a few bug fix releases before a version can be considered a good LTS. This gives us one month to release additional bugfix releases for N.10.x in case it’s needed.
…
Since we now have 2 bugfix releases planned in December before EOY, I propose to change the strategy to always announce the LTS at the end of the year, once N.10.2 is released.
I consider that 2 bug fix releases is enough to call it LTS as a general rule. In the event that we’d find a blocker we’d release a new bugfix release quickly.
** Update [[the download page>>xwiki:Download.WebHome]] to have a single version (the LTS)
** Update API pages: [[Platform API>>platform:DevGuide.API]] and [[Rendering API>>rendering:Main.JavaDoc]]
** Make sure that N.10.2 is announced as the LTS in the forum post for the N.10.2 release
** Make sure that N.10.2 is announced as the LTS in the blog post for the N.10.2 release
** Check if there are important issues to release in the previous LTS branch and schedule a last release if need be
** Change the Debian LTS repository to point to N.10.2
** Update the [[official Docker XWiki image>>https://github.com/docker-library/official-images/blob/master/library/xwiki]] to change the ##lts## tags to point to N.10.2
*** Remove the ##lts## tags from the previous LTS version and move them to the new LTS version
*** Keep the ##stable## tags in the new LTS version until we release N+1.0
*** Keep the previous LTS version definitions until we release N+1.0