Release cycles

At Redcrest Solutions GmBH we choose to have a continuous update process instead of having “releases”.

Advantages of the continuous update

• Smaller changes over time
• Quick react to user feedback and bug fixing
• Easier to develop

Drawbacks

• At any point we may introduce new bugs, which the day before were not there (where in the release cycle you know when those could pop up).
• Every day it may be a bit different, and could make people feel a bit unsecure.

Delayed deployement

We can offer an alternate workflow in the sense we will continue to deploy every release on the test instance for you, and you will be then in charge to deploy the latest version (running on the test instance) to your production instance with a convenient page within Flying Fleet. Database upgrades will be carried over at the time you upgrade. However you will be in charge of the testing on the test instance to be sure it fits your need before you deploy it.

If this option is choosen, note that any bug fix or software security update will NOT be deployed by our staff on the production instance. Only OS upgrades / updates are performed.

All the updates (even those not yet deployed) are visible in your "System" / "Commits" page. Allow some time for the first load.