[Tiki-devel] The Tiki lifecycle is optimal (since 2018)

[email protected]
Newsgroups gmane.comp.cms.tiki.devel
Message-ID <[email protected]>
Dear Tiki community,

4 years ago, I wrote a summary of our decision at a TikiFest:
https://tiki.org/forumthread69969-A-large-majority-of-the-TikiFesters-want-to-move-to-a-3x8-month-lifecycle

Here is our process in great detail: https://tiki.org/Versions

I think it's optimal, and we should just continue like this for the 
foreseeable future.

As of now,
* 18x and 21x are security-fixes only
* 24x is bug fixes and minor, self-contained enhancements
* trunk (future 25x) is for major developments

For those that may have concerns that older LTS versions take away a lot 
of energy from developers that could be used for building the future: As 
we can see in commit logs, development on older versions naturally slows 
down. Any activity in old branches was either important (ex.: MySQL 8 
support, security, etc.) or with no risk of regression.
https://gitlab.com/tikiwiki/tiki/-/commits/21.x
https://gitlab.com/tikiwiki/tiki/-/commits/18.x

So I consider our process as "optimal" and can't think of a way to 
improve it. Any changes would improve some aspects but would have 
drawbacks.

Best regards,

Marc
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.