Development process

Release process

For each release we create a project with a milestone. At a certain point it will be decided which bugs and enhancements and features will make it into the release. This will be highly dependant on who is willing and able to invest time into a bug, enhancement or new feature. At a certain point in time the maintainer of the project (Pim) will freeze the release. From that point on no new bugs/enhancements/features will be added to the release. From that moment onward we will only focus on finishing the release. The only exception might be a critical bug that pops up. After this freeze-date all other bugs, features and enhancements will move to the next release or further.

When all bugs, features and enhancements are done for a release and they are individually tested, they will be merged to the development branch and called an 'unstable release' which will be thoroughly tested. Any critical bugs that come forward out of this release have to be crushed before we can call it a 'stable release' and move it to the master branch. Non-critical bugs that occur might be postponed for the next release. They will however be noted as "known issues" on the release notes for the new release.

Branches

How we manage branching in more detail is described on the branching wiki page.