Branches - Revision history

Ubit: /* Git Repos */

2023-11-27T16:34:36Z

‎Git Repos

2023-11-27T16:34:21Z

‎Repositories in the Primary Git

2023-11-27T16:32:20Z

‎Repositories in the Primary Git

2023-11-27T16:31:00Z

‎Git Repos

2023-11-27T16:29:56Z

‎Repositories in the Primary Git

2020-10-17T10:17:46Z

‎New minor Releases

2020-10-17T10:16:43Z

‎New major Releases

2020-10-17T10:15:51Z

‎Other Branches

2020-10-17T10:14:52Z

‎Other Branches

2020-10-17T10:12:37Z

‎Old procedure ( prior to 0.9x)

@@ Line 11: / Line 11: @@
 * [https://github.com/opensim/ '''Mirror''' OpenSimulator Github Repo]
 * [https://bitbucket.org/opensimulator/opensim/src/master/ '''Mirror''' OpenSimulator Bitbucket Repo]
 === Repositories in the Primary Git ===

← Older revision		Revision as of 16:34, 27 November 2023
Line 18:		Line 18:

	This page outlines the repository branches and tags; what they are for, and our policy for what goes into it.		This page outlines the repository branches and tags; what they are for, and our policy for what goes into it.
−
−	* [https://bitbucket.org/opensimulator/libopenmetaverse/src/master/ libOpenMetaverse for OpenSimulator] - our fork of libOpenMetaverse

	Also read		Also read

@@ Line 19: / Line 19: @@
 This page outlines the repository branches and tags; what they are for, and our policy for what goes into it.
-* [https://bitbucket.org/opensimulator/libopenmetaverse/src/master/ forked libOpenMetaverse] - our fork of libOpenMetaverse
+* [https://bitbucket.org/opensimulator/libopenmetaverse/src/master/ libOpenMetaverse for OpenSimulator] - our fork of libOpenMetaverse
 Also read

@@ Line 10: / Line 10: @@
 * [http://opensimulator.org/viewgit/ '''Primary''' OpenSimulator Git Repo]
 * [https://github.com/opensim/ '''Mirror''' OpenSimulator Github Repo]
 === Repositories in the Primary Git ===

← Older revision		Revision as of 16:29, 27 November 2023
Line 17:		Line 17:

	This page outlines the repository branches and tags; what they are for, and our policy for what goes into it.		This page outlines the repository branches and tags; what they are for, and our policy for what goes into it.
		+
		+	* [https://bitbucket.org/opensimulator/libopenmetaverse/src/master/ forked libOpenMetaverse] - our fork of libOpenMetaverse

	Also read		Also read

@@ Line 47: / Line 47: @@
 === New minor Releases ===
-Minor releases will contain small changes or more fixes to previous release.<br>
+Minor releases will contain small changes or fixes to previous release.<br>
 In many cases master branch does correspond to the required release in this case it is just like a new release<br>
 On occasions it may be required to only include selected commits or even unique special code, in this case:

@@ Line 41: / Line 41: @@
 A new release is created for main master code.<br>
-* A tag with the full release name is added. (example 0.9.1.1).<br>
+* A tag with the full release version is added. (example 0.9.1.1).<br>
 * A Branch named as the release number is created.<br>
 * Master version is changed to at least the next minor number.<br>

@@ Line 70: / Line 70: @@
 === Other Branches ===
-Other branches mainly contain temporary development work, for example to develop new code without disturbing current master.
+Other branches mainly contain temporary development work, for example to develop new code without disturb current master
 '''Browse a list of all branches'''

@@ Line 63: / Line 63: @@
 Old procedure used extra names like '-Release' and '-postfixes' after the version name.<br>
-That allowed for confusing version identification.<br>
+All releases should have their own version number.<br>
-All releases should have its own version number.<br>
+Lower digits of a version name are clear and enough identification for minor changes and bug fixes<br>
 Something like  0.7.0.1-Release and 0.7.0.1-post-fixes was just redundant and confusing<br>
 Under new format this would be just 0.7.0.1 and 0.7.0.2<br>