Here is a summary of approach which is considered based on different proposals.
Table of Contents
ERP5 will move towards a formal release process. Here is a summary of approach which is considered based on different proposals. To understand the rationale, please read the references before posting
a comment or a question.
How¶
Required:
- tag based approach (ie. all patches are postponed until tag is released - tag has 0 errors in all tests)
- release manager must be ERP5 expert
Optional:
- single branch based approach (ie. backport of selected patches by branch maintainer). This requires much more human resources.
When¶
- learning curve (ie. easier to learn for beginners)
- community marketing (ie. potential contributors)
- business marketing (ie. potential customers)
- accelerating adoption of latest features (ie. make developers feel safe to upgrade)
Myths¶
Release are neither sufficient nor required for:
- providing stable software. More tests (unit, functional, etc.) within the existing public framework is the most efficient way to reach this goal.
- delivering stable solution to customer. Customer specific tests are the most efficient way to reach this goal (they also make the implementation process up to 10 times more productive).
- providing stable upgrade. Automatic upgrade tests are the most efficient way to reach that goal. The current unit test framework could be used for the purpose of testing upgrade automatically.
References¶
http://mail.nexedi.com/pipermail/erp5-dev/2007-September/001373.html
http://mail.nexedi.com/pipermail/erp5-dev/2007-September/001379.html
Related Articles¶