Release schedule
This page is meant to outline the release schedule used in Unknown Horizons.
Unknown Horizons uses a time based release schedule. That means every release will contain all changes made in a certain time frame (e.g. 3 months), after which a new version is released. This is unconnected to the amount of changes actually made. This is in contrast to a feature based release, where a release is made after a certain set of features is implemented.
Using a time based release schedule hinders feature creep. This means we will not be postponing a release because of x,y,z still having to be completed. This enables us to stick to a release schedule, which enables a set of benefits:
- Trust and anticipation by users, that they will see a new release (possibly containing their changes) seeing the light of day in due time
- Ensure ongoing progress to the outside, keeping people outside the core dev team in the loop of what is happening
- Makes sure that the release cycle is as automated as possible
- Gives translators, artists etc. a fixed time until which they have to have submitted their contributions to have them in the release
The main problem with this approach is that we will be completely dependent on FIFE releases. This can only be avoided by always working with the latest release of FIFE and never using svn-only features, as these could turn into a blocker for our time slot based release. For the best benefit of Unknown Horizons (and probably FIFE too), FIFE should also change their release cycle to something more regular and thereby becoming more reliable as an engine/library.
Unknown Horizons ships one release every three months, starting with March, 1st 2013.
Hopefully with a new FIFE release out by then, we can release all the changes accumulated in the past 4 month since we branched the release branch. We might need to brand that release as somewhat unstable. From then on we can stick to a three month release cycle. Because we do not want to be dependent on FIFE releasing new stuff, we have to stick to the official latest FIFE release and not use SVN changes, as long as they are not officially released.
