Release Cycle

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
 
<br />
 
<br />
  
−
{{obsolete}}
+
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.
  
−
This is the current proposed OpenSim lightweight Release Cycle recipe.
+
Here are the release cycle steps
  
−
The goal is to run a cycle that churns out recommended code snapshots with reasonably regular intervals, and with a minimum of work for any one human resource. It should be a community effort, and anyone should be able to move the cycle forward.
+
# '''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.
−
If you're not acquainted with svn revision numbering schemes, see [[On revisions, tags and branches]] for additional info.
+
# '''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.
−
The Cycle:
+
# '''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).
−
<ol>
+
# '''Produce a source package''' for the release candidate (optional).
−
<li>Developers and Testers work on <em>/trunk</em> ("testers" being defined as "users feeding off trunk", also lovingly known as "trunkheads")</li>
+
# '''Announce the branch''' in the opensim-dev mailing list
−
        <li>/trunk revisions will always have the [http://opensimulator.org/cgi-bin/viewvc.cgi/*checkout*/trunk/OpenSim/Framework/Servers/VersionInfo.cs Flavour] "Dev" reflected in the version info string.
+
# '''Gather feedback''' over a week or so. '''Make bug fixes''' if possible - critical showstopper bugs (e.g. server will never start up) ''have'' to be fixed
−
<li>Using the opensim-dev e-mailing list, developers and Testers identify identify and reach concensus on suitable release candidate revisions, from the repository history. (for example, people on [http://osgrid.org/ osgrid.org] discuss this on their weekly meet-ups)</li>
+
# '''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).
−
<li>This revision is branched off as a "release candidate" (to <em>/branches/0.6.5-rc1</em> in this case), version number is upped, flavour is changed to "rc1". Version number and flavour changes and committed <em>only to this branch</em>. We don't want to up the version number in trunk until we know we have a release.</li>
+
# '''Change the download wiki page''' to point to new release
−
        <li>A template e-mail is sent to the opensim-dev mailing list, stating that there is now an rc.</li>
+
# '''Produce binary packages''' and installers (optional)
−
<li>Testers now switch their focus to running the rc until they can give feedback on whether "rc <strong>sux</strong>" or "rc <strong>rox</strong>".
+
−
Key issues:
+
−
<ul>
+
−
<li>Has all version numbers been updated?</li>
+
−
<li>Does it play well with last version? Do we need to up the interface version as well?</li>
+
−
<li>Does it feel better or worse than last version?</li>
+
−
<li>Any critical errors that needs fixing first?</li>
+
−
</ul>
+
−
</li>
+
−
<li>If any <span style="text-decoration: underline;">critical but fixable</span> errors are found, these are fixed in trunk and the fixing revision is merged into the release candidate branch. (or vice versa, if that works out better)</li>
+
−
<li>If, even after this, testers agree that "rc sux" the project goes back to 1) to wait and look for the next rc (thusly named rc2)</li>
+
−
<li>If testers agree that "rc rox" the flavour of the current rc branch Flavour is changed to "Release", and this is tagged as "-release" (to <em>/tags/0.6.5-release</em> in this case)</li>
+
−
<li>The flavour of the "-rc1" branch is then changed to "Post_Fixes" and after this renamed to "-post-fixes"  (to <em>/branches/0.6.5-post-fixes</em> in this case) for continued service awaiting the next cycle. The svn rename lets us keep the revision history back thru the rc branch history.</li>
+
−
<li>The version number (and optionally interface version) uppage is merged back into trunk. (this is a minor merge which will probably always succeed without conflict) - but the Flavour is kept at "Dev" in the trunk.</li>
+
−
        <li>A template e-mail is sent out to the opensim-dev mailing list stating that there is now a new release.</li>
+
−
<li>The project goes back to 1)</li>
+
−
</ol>
+
−
The output of this would be named version flavours for each of these user categories:
+
−
<ul>
+
−
<li><strong>Grid/Region owners running services in production</strong>
+
−
 
+
−
 
+
−
Feed off "-post-fixes" if they want stability first, or off "-release" if they want a known 'upgrade track'.</li>
+
−
<li><strong>Developers</strong>
+
−
 
+
−
 
+
−
Feed off <em>/trunk</em> ("Dev"), or off -rcX or -post-fixes if they want some stability while hunting bugs or doing protoyping.</li>
+
−
<li><strong>Testers</strong>
+
−
 
+
−
 
+
−
Testers are committed to helping the devs find bugs at the prize of instabilities, crashes and loss of data. They therefore feed off the <em>/trunk</em> ("Dev") development branch or -rcX depending on whether there is an RC pending release or not. (ie, is the latest version an RC, use that, if not, use <em>/trunk</em>)
+
−
Everyone feeding off <em>/trunk</em> are collectively labeled 'testers', and any installation running on anything but a 'release' or 'post-fixes' revision is considered a 'test installation'.</li>
+
−
</ul>
+

Revision as of 13:31, 24 November 2009

Languages Languages: 

En.png English   De.png Deutsch


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

  1. Get informal feedback about current OpenSim stability. A good place to do this is the OpenSim weekly developer's meeting on osgrid.org.
  2. Announce the intention to start a release process to the opensim-dev mailing list.
  3. Branch <release name>-post-fixes from OpenSim Master in git. For example, 0.6.8-post-fixes.
  4. Change the version type in VersionInfo in OpenSim.Framework.Servers to RC1.
  5. 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).
  6. Produce a source package for the release candidate (optional).
  7. Announce the branch in the opensim-dev mailing list
  8. Gather feedback over a week or so. Make bug fixes if possible - critical showstopper bugs (e.g. server will never start up) have to be fixed
  9. 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).
  10. Change the download wiki page to point to new release
  11. Produce binary packages and installers (optional)
Retrieved from "http://opensimulator.org/index.php?title=Release_Cycle&oldid=15996"
Personal tools
General
About This Wiki