Loading...
 

Development Process

Challenges of any software project include: build vs integrate, and how to keep all the dependencies in sync.

One specific WikiSuite component criteria is to be "Multi-functional" / "All-in-one" to avoid complexity and plugin problems. Another specific strategy is to work closely with all components and improve the code upstream.

Here are some notes about each component.

Tiki 

Every 3rd release is LTS for 5 years.


Most cost-efficient process is to develop in trunk, in time for April and October releases.
Backporting is possible

Openfire Meetings and Jitsi Meet 

No fixed time frames for releases, but cadence is fast enough.
Openfire Meetings bundles several apps (Jitsi Meet is the big one), and it's a challenge to keep everything in sync.

ClearOS 

As a GNU/Linux operating system, there is a lot of flexibility in getting packages, but it's a slippery slope to dependency hell.
Upstream has a release every few years, and a very long support cycle. Tends to package older versions, which forces us to do things like: How to install a PHP version picker on ClearOS

Syncthing 

Syncthing follows a rapid release process. As a p2p app, if the protocol changes, old versions can't sync data with new versions. It is possible to set your Syncthing to get always the latest releases, or to have a slight delay.