Tuesday, March 3, 2009

Quick status update on ERP 2.50

My last blog post was focused on the status of Openbravo ERP 2.50. Since a month has gone by, I would like to give you a very quick status update on where we are now.

Since then, we had to modify our exit criteria to make it more reachable. In particular, we had to put a "cut off" date for the defects that we were planning to fix. We debated this both internally and in the Community and finally we settled with the following exit criteria:
  • Defects logged up to Feb 13th: 0 critical and major defect, less than 100 minor and trivial
  • Defects logged after Feb 13th: 0 defects with urgent priority
  • QA testing completed
  • Upgrader ready and tested
This criteria gave us a good provision for a) cleaning the backlog of old stuff and b) giving QA the flexibility to request fixes for as many show stoppers they feel are needed and hold the release until they are satisfied with its quality level.

We reached this exit criteria last week on February 24th. Since then, we have frozen the the development code line (Main, using the new Mercurial terminology) and are running various installation and upgrade tests with this final code.

We hope to release 2.50 Beta within this week.

2 comments:

Leon said...

Congratulation! We are looking forward OB2.5 Beta!

Vladislav Zhivkov said...

I've just published this news at Openbravo Bulgarian User Group Site (www.openbravobg.com) and at http://expert.idg.bg/.

I will continue my publications at two sites.