Openbravo ERP 2.40 continuous releases
Openbravo ERP has currently two major versions: 2.50 is the latest one and it’s actively developed. 2.40 is a maintenance release for Professional Edition users, and it mainly consists of bug fixes, with an average of 20 fixes per month.
These 2.40 updates are distributed as Maintenance Packs (MPs – a collection of bug fixes), with a frequency of one month during the first year and of two months during the second one (since November 2009). Starting from 2.40MP11 we are introducing a new concept of MPs. Instead of releasing bi-monthly updates we will release them on a bi-weekly basis, tested and verified by our Continuous Integration Framework. This is the workflow that this automated process follows:
- Mike reports an issue and it gets assigned to Ken, a Openbravo ERP developer.
- Ken fixes the issue and pushes the commit into the 2.40 Mercurial repository.
- Our build farm runs a set of tests on that changeset:
- Incremental update test on PostgreSQL and Oracle. This is important to test updates to this changeset.
- Full clean builds on PostgreSQL and Oracle. This is used to test new installations based on this new changeset.
- Verify the database consistency. This verifies that the database model matches exactly its definition in the XML files.
- Functional tests on PostgreSQL and Oracle. This runs a set of graphical on a web browser, powered by Selenium.
- Other minor sanity tests, such as checking that no database data is entered using the reserved ID ranges.
- If all the tests pass successfully, we tag and sign the release in the Mercurial repository, and later on replicate it into our Subversion mirror. If one test fails the system waits for new changesets and starts the process again.
- Mike gets notified about the availability of a new MP that includes a fix for the issue he reported.
These kind of MPs are easily identifiable by it’s version numbering, following the 2.40MPX.Y schema. As an example, we currently have released four, called 2.40MP11.1, 2.40MP11.2, 2.40MP11.3 and 2.40MP11.4.
What does this mean for a 2.40 user?
- We are reducing the delivery time. You get maintenance updates every two weeks.
- You get updates of the fixes you reported faster than ever.
- You update your 2.40 installation using the usual method (Subversion), this does not change.
Note that we are also planning to release two more “traditional” MPs during the 2.40 life cycle, that will consist of additional manual verifications. They will be called 2.40MP12 and 2.40MP13, scheduled for February and August 2010 respectively. Here’s a table that summarizes the 2.40 MP frequencies:
|2.40MP11||November 2009 (already released)|