Release Procedure

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
 
(8 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
* Work on whatever branch makes sense for the release.  
 
* Work on whatever branch makes sense for the release.  
** A new major release is usually cut on a newly created branch called v-v-v-post-fixes.
+
** A new major release is usually cut on a newly created branch called v.v.v-post-fixes.
** Minor releases are done over those existing v-v-v-post-fixes branches.
+
** Minor releases are done over those existing v.v.v-post-fixes branches.
 
** In either case, '''don't forget to change the info in OpenSim/Framework/VersionInfo.cs'''.  
 
** In either case, '''don't forget to change the info in OpenSim/Framework/VersionInfo.cs'''.  
  
Line 16: Line 16:
 
Once you do this setup once, you can use it for all subsequent releases
 
Once you do this setup once, you can use it for all subsequent releases
  
* Follow the instructions in README, adjusting the commands there for the appropriate release number.  
+
* Follow the instructions in README, adjusting the commands there for the appropriate release and branch identifiers.  
 
** For example,
 
** For example,
  In README: ./release1.pl opensim-0.8.2.0-rc1 0.8.2-post-fixes
+
  In README:   ./release1.pl opensim-0.8.2.0-rc1 0.8.2-post-fixes
  Your command: ./release1.pl opensim-0.9.0.1 0.9.0-post-fixes
+
  Your command: ./release1.pl opensim-0.9.0.1     0.9.0-post-fixes
In this case you are replacing the version identifier  "0.8.2.0-rc1" with the version identifier "0.9.0.1", and the branch identifier "0.8.2-post-fixes" with "0.9.0-post-fixes"
+
In this case you are replacing the version identifier  "0.8.2.0-rc1" with the version identifier "0.9.0.1", and the branch identifier "0.8.2-post-fixes" with "0.9.0-post-fixes".
Use those numbers consistently for all the commands in README
+
Use those identifiers consistently for all the commands in README
 +
 
 +
'''Advice''': copy the README file into an editor, make the identifier changes there, and then simply copy-paste the commands to the command line.
  
 
* That's it! At the end, you'll have the releases placed properly in the distribution directory of the web server. Make sure they have read perms for everyone.
 
* That's it! At the end, you'll have the releases placed properly in the distribution directory of the web server. Make sure they have read perms for everyone.

Latest revision as of 14:47, 12 September 2017

[edit] How to make OpenSim releases

  • Work on whatever branch makes sense for the release.
    • A new major release is usually cut on a newly created branch called v.v.v-post-fixes.
    • Minor releases are done over those existing v.v.v-post-fixes branches.
    • In either case, don't forget to change the info in OpenSim/Framework/VersionInfo.cs.
  • Login to opensimulator.org. If this is the first time you make a release:
    • Copy /home/diva/releases/*.pl and /home/diva/releases/README to your own releases directory.
    • Under your releases directory, make a clone of opensim into a directory called opensim-git. Your releases directory should look like this:
~/releases
   README
   *.pl
   opensim-git/

Once you do this setup once, you can use it for all subsequent releases

  • Follow the instructions in README, adjusting the commands there for the appropriate release and branch identifiers.
    • For example,
In README:    ./release1.pl opensim-0.8.2.0-rc1 0.8.2-post-fixes
Your command: ./release1.pl opensim-0.9.0.1     0.9.0-post-fixes

In this case you are replacing the version identifier "0.8.2.0-rc1" with the version identifier "0.9.0.1", and the branch identifier "0.8.2-post-fixes" with "0.9.0-post-fixes". Use those identifiers consistently for all the commands in README

Advice: copy the README file into an editor, make the identifier changes there, and then simply copy-paste the commands to the command line.

  • That's it! At the end, you'll have the releases placed properly in the distribution directory of the web server. Make sure they have read perms for everyone.
Personal tools
General
About This Wiki