All,
we want to freeze 2.50 this Friday and we are making good progress towards
the exit criteria that I described last week.
As of now, we have 165 defects open with the following break down:
- Critical: 5
- Major: 37
- Minor: 109
- Trivial: 14
Let me clarify what we need to do in order to achieve code freeze:
1. Reduce the open defects to 0 critical and major and less than 100
trivial and minor
2. Complete the QA test
3. Complete the testing of the upgrader
4. Upgrade the demo data to 2.50
If these objectives are met, this week instead of creating 2.50 alpha,
Release Management will create the 2.50 beta stabilization branch.
Based on that branch, next week QA will perform installation, upgrade and
smoke testing and will require the fix of selected defects.
Once that activity is complete (target the subsequent Friday, February
27th), we will create and release the 2.50 beta Community Appliance and we
will publish the tag.
Let me know if you have any question.
Thanks,
Paolo
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Openbravo-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development
