Fork me on GitHub
 

All releases for ImpressCMS will go through the following Release Cycle:



  • Alpha Stage (Alpha 1, and possibly, Alpha 2, etc.)

  • Beta Stage (Beta 1, and possibly, Beta 2, etc.)

  • Release Candidate Stage (RC 1, and possibly, RC 2, etc.)

  • Final Stage


Alpha Stage


Alpha releases are solely for development and testing purposes. Those releases can be as unstable as can be. Bugs can be fixed during this stage but we will most likely use the Beta stage to fix bugs.


An Alpha release is not suitable for use on a live site.


Committing Restrictions


The only restriction there is regarding committing in an Alpha stage is to stick as much as possible with the Roadmap.


Beta Stage


When the developers are ready to release a new version of ImpressCMS, a Beta release will be the first phase of the official release cycle. A new branch in the SVN repository will be created with the name impresscms_x.y (where x.y is the new version number).


The release of a Beta version will follow our Release Procedures. During the Beta phase (and as a general rule as well), any bugs will be initially reported in the Current Release forum and validated by other users. Should the bug be verified, it will be added to the bug tracker.


Work on the bug fixes will be done in the release branch, not in the trunk.


A Beta release is not suitable for use on a live site. Generally, after 2-3 weeks of the release, the developers will decide if a new Beta needs to be released or if we should move to the Release Candidate stage of our Release Cycle.


Committing Restrictions



  • No new features are to be introduced during Beta stage

  • Only bug fix are to be committed during this stage

  • New features can always be committed in the Trunk


Release Candidate


When the Beta release(s) have been sufficiently tested and all open bugs have been addressed, we will move forward to the Release Candidate stage. In this phase, the same branch from the Beta phase is used in the ImpressCMS SVN.


The release of a Release Candidate version will follow our Release Procedures. During the RC phase only Show Stoppers Bug can be fixed. All other bugs will need to wait for the next Version Number.


In all cases, any bugs will be initially reported in the Current Release forum and validated by other users. Should the bug be verified, it will be added to the bug tracker.


Work on the Show Stopper bug fixes will be done in the release branch, and all other bugs fill be fixed in the Trunk. A Release Candidate release is not suitable for use on a live site.


Committing Restrictions



  • Only Show Stoppers Bug may be committed in the release branch

  • All other bug fixes can always be committed in the Trunk


Final Release


After the Release Candidate has been thoroughly tested and no Show Stopper bugs are present anymore, a Final version will be released. The release of a Final version will follow our Release Procedures.

Last modified on 2016/12/26 by Anonymous
Comments
The comments are owned by the poster. We aren't responsible for their content.