Quality Insurance:Testing Process
From Wiki
Contents |
Explanation of the Versions
The development of OpenERP follows two distinct branches:
- Stable: a new version is published every year. This version is intended to be put in production, only bugfixes are applied in this version.
- Development (sometimes called the trunk): It will contain all the latest functionalities and modules. It is intended for testing purpose only, until it is stabilized as the next stable version.
You can get more information on how we manage each version in the community process .
Introduction
Timeline
A new stable version is published every year:
- May: Community Meeting
- Define missing and urgent bugfixes and features
- Tiny and Partners Choose modules from contrib and extra addons that will integrate official addons
- Define precise timeline and tasks assignation
- July: Branch the trunk to the new stable version
- You can not add new features in the futur stable
- Only bugfixes are accepted in this new branch
- August: Publish first releases candidates
- September: Publish the new stable version
Processes
Community Meeting
Participants: Everybody
Goals:
- Define exact release timeline
- Define required tasks for new version
- Select official addons
Branching to new stable
Goals:
- After branching, no new features accepted
- Bugfix period
Release Candidates
Goals:
- Publish a version to be tested by the community
- Different release candidates, every 2 weeks
Stable Version
Goals:
- Publish when everything is perfect


