Release Cycle
From OpenSimulator
(Difference between revisions)
| Line 14: | Line 14: | ||
# '''Produce a source package''' for the release candidate (optional). | # '''Produce a source package''' for the release candidate (optional). | ||
# '''Announce the branch''' in the opensim-dev mailing list | # '''Announce the branch''' in the opensim-dev mailing list | ||
| − | # '''Gather feedback''' over a week or so. '''Make bug fixes''' if possible. Critical showstopper bugs (e.g. server | + | # '''Gather feedback''' over a week or so. '''Make bug fixes''' if possible. Critical showstopper bugs (e.g. server won't start up) ''have'' to be fixed. |
# '''Change the version type''' to Release | # '''Change the version type''' to Release | ||
# '''Produce OpenSim source code packages''' after a successful test period and ''place on the website''' at http://opensimulator.org webserver (this needs further documentation since the automated production process is currently broken). | # '''Produce OpenSim source code packages''' after a successful test period and ''place on the website''' at http://opensimulator.org webserver (this needs further documentation since the automated production process is currently broken). | ||
Revision as of 12:40, 24 November 2009
 |
Languages: |
|
OpenSim has a lightweight release cycle right now. This allows us to get code out to people quickly, as befits the alpha status of the project.
Here are the release cycle steps
- Get informal feedback about current OpenSim stability. A good place to do this is the OpenSim weekly developer's meeting on osgrid.org.
- Announce the intention to start a release process to the opensim-dev mailing list.
- Branch <release name>-post-fixes from OpenSim Master in git. For example, 0.6.8-post-fixes.
- Change the version type in VersionInfo in OpenSim.Framework.Servers to RC1.
- Change the release number in OpenSim trunk to the next possible future release (e.g. 0.6.9 if this release process concerns 0.6.8).
- Produce a source package for the release candidate (optional).
- Announce the branch in the opensim-dev mailing list
- Gather feedback over a week or so. Make bug fixes if possible. Critical showstopper bugs (e.g. server won't start up) have to be fixed.
- Change the version type to Release
- Produce OpenSim source code packages' after a successful test period and place on the website at http://opensimulator.org webserver (this needs further documentation since the automated production process is currently broken).
- Change the download wiki page to point to new release
- Produce binary packages and installers (optional)
- Change the version type to Post_Fixes
