Release Cycle - Revision history

Manni at 10:23, 4 December 2023

2023-12-04T10:23:18Z

2021-12-05T14:30:42Z

2021-12-05T14:25:10Z

2021-12-05T14:23:40Z

2021-12-05T14:23:02Z

2021-12-05T14:21:25Z

2021-12-05T14:20:27Z

2021-12-05T14:15:10Z

2021-12-05T14:12:18Z

2021-12-05T14:10:17Z

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Quicklinks}}
+{{Quicklinks|Release Cycle}}
 <br />

@@ Line 11: / Line 11: @@
 On Git, at the release point, we;
 * create a new branch with the code to release and names as the release version, for example 0.9.2.0
-* change the version type to Release on the VersionInfo.cs of the release branch
+* on the release branch, change the version type to Release in the VersionInfo.cs
-* change version information on the needed source files (VersionInfo.cs, ServerReleaseNotesURL in OpenSimDefaults.ini, etc)  and commit to master
+* on master branch, change version information on the needed source files (VersionInfo.cs, ServerReleaseNotesURL in OpenSimDefaults.ini, etc)
-* add a tag with the new version with Dev suffix, for example 0.9.2.1Dev
+* on master branch, add a tag with the new version with Dev suffix, for example 0.9.2.1Dev
 add a release notes page for the new version on wiki as ServerReleaseNotesURL

@@ Line 12: / Line 12: @@
 * create a new branch with the code to release and names as the release version, for example 0.9.2.0
 * change the version type to Release on the VersionInfo.cs of the release branch
-* change version information on the needed source files (VersionInfo.cs, ServerReleaseNotesURL''' in OpenSimDefaults.ini, etc)  and commit to master
+* change version information on the needed source files (VersionInfo.cs, ServerReleaseNotesURL in OpenSimDefaults.ini, etc)  and commit to master
 * add a tag with the new version with Dev suffix, for example 0.9.2.1Dev

@@ Line 21: / Line 21: @@
 Add the release and new version to Mantis versions field
-Then update the rest of wiki so it points to the new release
+Update the rest of wiki so it points to the new release
-Then run to a remote island without telephones or internet
+Run to a remote island without telephone or internet

@@ Line 19: / Line 19: @@
 Produce the release source and binary packages and place on the website at http://dist.opensimulator.org
-Create a field for release in Mantis
+Add the release and new version to Mantis versions field
 Then update the rest of wiki so it points to the new release

@@ Line 9: / Line 9: @@
 We make a new release when the code state and received feedback justifies one.
 Changes on the minor number of the version will usually mean a release with mostly "bug fixes"
-# On Git, at the release point, we;
+On Git, at the release point, we;
 * create a new branch with the code to release and names as the release version, for example 0.9.2.0
 * change the version type to Release on the VersionInfo.cs of the release branch
@@ Line 15: / Line 15: @@
 * add a tag with the new version with Dev suffix, for example 0.9.2.1Dev
-# Produce OpenSimulator source and binary packages and place on the website at http://dist.opensimulator.org
+add a release notes page for the new version on wiki as ServerReleaseNotesURL
-# Then update mantis and the wiki, etc
+Produce the release source and binary packages and place on the website at http://dist.opensimulator.org
-# Then run to a remote island without telephones or internet
+Then update the rest of wiki so it points to the new release