Releases
Schedule
We aim at keeping this frequency for releases. However dates may slip according to needs
- trunk: every 6 weeks (~8 / year)
- 1.22: only when needed due to high priority issues
Strategies
For a full discussion around these topics see in oak-dev archives.
- trunk will be considered stable
- only releases from trunk other than existing branches
- any previous release from trunk will be automatically deprecated
Branching
Branching will not happen other than in specific circumstances. Such as, but not limited to:
- incompatible API changes
- incompatible JVM changes
- updates to dependencies that break backward compatibility
In short: most probably it will always be around non-backward-compatible changes.
Anyhow in such cases the branching is not automatic and will be discussed between PMCs a best course of actions. Alternatives may be a different way to implement something breaking.
Version Numbers
- Released versions will be in the format of
Major.Minor.Patch. - Note that these project version numbers are mostly irrelevant for OSGi, in which case only the package version numbers are important.
- Any new official release will be always even: 1.12.0, 1.14.0, 1.16.0, …, 2.0.0, 2.2.0 etc.
- A release will always be with a patch number (the last part) of
.0. This ease OSGi deployments. - In case of branching the increased part will always be the PATCH so:
1.16.0,1.16.1,1.16.2, etc.