-
Notifications
You must be signed in to change notification settings - Fork 30
Tool chain Release Process
Cecile Braunstein edited this page Feb 6, 2014
·
12 revisions
The basic release process of the OpenETCS tool chain proceeds as follow:
-
- Create a milestone after every Sprint (every two weeks) : Every sprint terminates with a Milestone releases
-
- Select a date for the next Release
-
- Decide on the next release contents with the users: The next milestone releases will be then Release candidates
A milestone will
- Correct bug reported in the issue tracker (tag: "bug report")
- Implement new functionalities from the issue tracker (tag: "Feature request")
A list of all the steps are given here: Checklist
At the end of each milestone releases, WP participants should at least try to open and/or update the new milestone releases.
A set of test for each feature (plug-ins and tools) should be provided.
- Select a Release date
- Decide the minimum contents
- Create release candidates (see the checklist for milestone release)
- Add RC qualifier
- Test all features (plugin and tools)
- Report Bugs
- Fix bug