View source | Discuss this page | Page history | Printable version   

Openbravo Design and Development Process/Launch


Openbravo Release Cycle

The launch phase covers all the steps that are necessary to deliver a successful release to the market, including (but not limited to):

Openbravo solutions are released on a quarterly basis. In the case of the Openbravo Commercial Suite (Openbravo for Retail) versions are released as 3.0RRXXQY, where:

Release Cycle.jpg

As shown in the image above, the duration of a release cycle is seven months. For instance, and in the case of Openbravo Commercial Suite 18Q4 design and development activities started dated on 1st June 2018 and will finish at release dated on December 31st, 2018.

Release phases

The release process consists of the following phases

Openbravo strongly recommends that only releases that have reached CS are used in production environments

In summary, Openbravo will release Confirmed Stable (CS) releases in March (i.e RR18Q1), June (i.e. RR18Q2), September (i.e. RR18Q3), and December (i.e. RR18Q4) on a yearly basis.

Early adopters testing (Innovators program)

As already mentioned Openbravo has stablished an innovators program based on what there is a maturation cycle to evolve Openbravo releases from QAA to Confirmed Stable, in collaboration with a set of Openbravo end clients.

These clients have access to the corresponding release in QAA status for them to use it and help Openbravo to mature it.

QAA releases have passed automated tests, all fixed issues have been individually verified and the QA team has completed a set of manual tests to identify further improvement.

When it reaches the QAA stage, the release is not yet available for a wide audience but it can already be used for production purposes for those who have a particular interest, explicitly assuring full alignment with the end client.

As part of the Innovators program, interested Partners will receive support in the update process of a customer’s production environment to the current QA Approved release.

For additional information, please review this Openbravo blog post.

Openbravo Release Notes

Every time Openbravo releases a new version of its Business or Commerce solutions, all what it contains it is documented in the corresponding Release Notes wiki page.
Release Notes wiki page informs about the date when a version was published as well as its maturity status.

It is important to remark that within Openbravo release note wiki page, there are direct links to what a given release includes, for instance 18Q4.

New versions of Openbravo Commerce Suite can include:

Maturity status

Openbravo solutions can be delivered on different maturity status:

Professional instances of Openbravo are defaulted to just accept versions in Confirmed Stable maturity status, as Confirmed Stable modules are modules that have been in use with customers for an extended period of time and are therefore proven by real world usage. Restricting access to modules in this status is recommended to organizations that prefer safety over the benefits of adopting new functionality closer to the leading edge of innovation.

Emergency releases

Apart when required there are out of schedule emergency releases which are used to for targeted fixing of very important bugs. Typically on the 15th every month release teams checks if any such fixes are pending to be published and prepares and extra release with those.

Those releases can be identified by their version which is constructed as follows 3.0RRXXQY.Z, where :

and will run through the same maturity status and release process.

Example the release named 3.0RR17Q2.1 is based on the initial base release 3.0RR17Q2 and contains only small set of targeted fixes on top. All those fixes will be fixed and verified by the corresponding engineering team and QA team will run once more all manual and automated tests, all of that within the same release cycle.

Retrieved from ""

This page has been accessed 1,351 times. This page was last modified on 22 November 2018, at 14:49. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.