Release Cycle
From OpenSimulator
(Difference between revisions)
m (Robot: Cosmetic changes) |
m (Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name) |
||
| Line 3: | Line 3: | ||
<br /> | <br /> | ||
| − | + | OpenSimulator 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 | Here are the release cycle steps | ||
| − | # '''Get informal feedback''' about current | + | # '''Get informal feedback''' about current OpenSimulator stability. Good places to do this are at the OpenSimulator weekly developer's meeting on osgrid.org and in the #opensim-dev IRC channel. |
# '''Announce the intention''' to start a release process to the opensim-dev mailing list. | # '''Announce the intention''' to start a release process to the opensim-dev mailing list. | ||
| − | # '''Branch''' <release name>-post-fixes from | + | # '''Branch''' <release name>-post-fixes from OpenSimulator Master in git. For example, 0.6.8-post-fixes. |
# '''Change the version type''' in VersionInfo in OpenSim.Framework.Servers to RC1. | # '''Change the version type''' in VersionInfo in OpenSim.Framework.Servers to RC1. | ||
| − | # '''Change the release number''' in | + | # '''Change the release number''' in OpenSimulator trunk to the next possible future release (e.g. 0.6.9 if this release process concerns 0.6.8). |
# '''Produce a binary package''' for the release candidate. | # '''Produce a binary package''' for the release candidate. | ||
# '''Create a field for release in Mantis''' | # '''Create a field for release in Mantis''' | ||
# '''Gather feedback''' over 2 weeks or so. '''Make bug fixes''' if possible. Critical showstopper bugs (e.g. server won't start up) ''should'' be fixed. | # '''Gather feedback''' over 2 weeks or so. '''Make bug fixes''' if possible. Critical showstopper bugs (e.g. server won't start up) ''should'' be fixed. | ||
# '''Change the version type''' to Release | # '''Change the version type''' to Release | ||
| − | # '''Produce | + | # '''Produce OpenSimulator source and binary 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 wiki pages''' to point to new release. This includes both the download page and the link on the front page. | # '''Change the wiki pages''' to point to new release. This includes both the download page and the link on the front page. | ||
# '''Change the version type''' to Post_Fixes | # '''Change the version type''' to Post_Fixes | ||
[[Category:Development]] | [[Category:Development]] | ||
Revision as of 22:56, 3 March 2012
 |
Languages: |
|
OpenSimulator 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 OpenSimulator stability. Good places to do this are at the OpenSimulator weekly developer's meeting on osgrid.org and in the #opensim-dev IRC channel.
- Announce the intention to start a release process to the opensim-dev mailing list.
- Branch <release name>-post-fixes from OpenSimulator 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 OpenSimulator trunk to the next possible future release (e.g. 0.6.9 if this release process concerns 0.6.8).
- Produce a binary package for the release candidate.
- Create a field for release in Mantis
- Gather feedback over 2 weeks or so. Make bug fixes if possible. Critical showstopper bugs (e.g. server won't start up) should be fixed.
- Change the version type to Release
- Produce OpenSimulator source and binary 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 wiki pages to point to new release. This includes both the download page and the link on the front page.
- Change the version type to Post_Fixes
