This is a draft of an article which will be published on tiki.org/articles
Retiring the past / spring cleaning
Tiki recently turned 20!
And we released Tiki25, which is the most important release ever.
- Biggest: most work into a release
Each version, we review proposals: Endangered features
AdoDB support is deprecated. Remove before branching 28.x.
The server for Git and SVN combined workflow will be retired
This is our 4th version control setup (cvs -> svn- -> svn-Allura -> GitLab)
Add ideas from https://gitter.im/tiki-org/community?at=63cd5bc5ec2bfc628669d65f
Rule no x commit early and often is not the same with Git
A commit has way more content/value than a commit in the old days
"Wiki Way to software development" has evolved.
IRC -> WikiSuite.chat experiment (XMPP) -> Gitter -> Gitter/Matrix
- All profiles for unsupported versions of Tiki will be deleted. Already applied profiles are, as always, unaffected.
- We will review the remaining profiles to clean up https://profiles.tiki.org/
- We will leverage the recently created Tiki Profiles Tester
- Decide about the lifecycle of a profile. Generally, a profile works for several future versions. But when it doesn't, what is the pattern? Some examples:
To review all of Hetzner
- tiki.org mail server migration
- WYSIWYG and Markdown
- Bootstrap 5 (refine the integration)
- Can we scan for unused classes?
- Manticore Search (explain why we added)
- Security audit (which will mean backports to many Tiki versions)
- Remove info on *.tiki.org which relates to end of life versions
- Clean our backlog: https://gitlab.com/groups/tikiwiki/-/merge_requests (79 as of 2023-02-17. And way too many are beyond 4 weeks old)
- Unified Admin Backend