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

ERP/Release Life Cycle



This article describes the Openbravo releases in terms of their life cycle and support plan: initial release, maintenance mode and end-of-life.

Release strategy

Generally speaking there are two main release strategies:

  1. Time based cycles: release software with a fixed periodicity. Ubuntu is an example of this strategy, they release a new major version every 6 months.
  2. Feature driven cycles: release software following the "It's ready when it's ready" strategy. Debian is an example of this strategy, they have a quality based criteria for considering a release as stable.

Openbravo uses a mixture between the time based and feature driven release strategies, following a criteria as follows:


So far Openbravo ERP has released 4 major releases:

Version Maturity status Current release stage Current release frequency Release Date End of life date
3.0 Production ready Preventive Support Quarterly 15/06/2011 undefined (*)
2.50 Production ready Preventive Support on demand 16/04/2009 undefined (*)
2.40 Production ready Discontinued Discontinued 08/10/2008 31/12/2014
2.3x Production ready Discontinued Discontinued 5/11/2007 10/12/2009

Bulbgraph.png   (*): the end-of-life date calculation depends on the second to next major version. For 2.50 this will be calculated once 3.1 is released, and in the same manner 3.0's end-of-life date depends on the future 3.2 release.

Some of the columns require additional explanations of their possible values and meanings:


ERPs are mission critical software and this is why Openbravo has designed a support plan according to this necessity. This is the root idea from which some additional key requirements flourish with the goal of creating the best possible Openbravo support plan:

Regular Maintenance Packs (MPs) look to increase the stability of the product and fix the customer's issues according to the SLAs. In terms of timings, we have defined 3 stages, explained in detail as follows.

Preventive Support

Preventive Support lasts till the first ship date of the second to next release plus six months with a minimum duration of 30 months (2.5 years) from first ship date:

Minimum duration: 2.5 years.

Reactive Support - Phase 1

Duration: 1 year.

Reactive Support - Phase 2

Duration: 2 years


Releases timeline


IMPORTANT NOTE: Openbravo 3.1 and 3.2 and fictional releases, they are not planned nor developed yet. They are listed here to illustrate the support plans for 2.50 and 3.0 if the future 3.1 and 3.2 were released in 04/2012 and 04/2013 respectively.

Release Team

See the Release Management page for more information about the team members as well as the team's mission statement, goals and roles.

Retrieved from ""

This page has been accessed 19,036 times. This page was last modified on 16 June 2020, at 11:19. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.