Branches/de - Revision history

Manni at 08:15, 2 December 2023

2023-12-02T08:15:24Z

Manni at 08:14, 2 December 2023

2023-12-02T08:14:13Z

Manni: /* Tags */

2023-12-02T08:12:33Z

‎Tags

Manni: /* Branches */

2023-12-02T08:11:45Z

‎Branches

Manni: /* Branches and Tags in the Git Repo */

2023-12-02T08:00:21Z

‎Branches and Tags in the Git Repo

Manni: Created page with "NOTOC {{Quicklinks}} == Branches and Tags in the Git Repo == OpenSimulator uses Git for its source code repository. The repository contains various branches and tags use..."

2023-12-02T07:54:41Z

Created page with "__NOTOC__ {{Quicklinks}} == Branches and Tags in the Git Repo == OpenSimulator uses Git for its source code repository. The repository contains various branches and tags use..."

New page

__NOTOC__
{{Quicklinks}}

== Branches and Tags in the Git Repo ==

OpenSimulator uses Git for its source code repository. The repository contains various branches and tags used to identify development branches and release branches of the code. The primary git repository is hosted on the opensimulator.org domain. A mirror is maintained on Github. The Github repo is sync'ed with the primary every 10 minutes.

=== Git Repos ===

* [http://opensimulator.org/viewgit/ '''Primary''' OpenSimulator Git Repo]
* [https://github.com/opensim/ '''Mirror''' OpenSimulator Github Repo]
* [https://bitbucket.org/opensimulator/opensim/src/master/ '''Mirror''' OpenSimulator Bitbucket Repo]
* [https://bitbucket.org/opensimulator/libopenmetaverse/src/master/ libOpenMetaverse for OpenSimulator] - our fork of libOpenMetaverse

=== Repositories in the Primary Git ===

* [http://opensimulator.org/viewgit/?a=summary&p=opensim opensim] - the OpenSimulator source code
* [http://opensimulator.org/viewgit/?a=tree&p=opensim-libs opensim-libs] - forks of third party libraries used in building OpenSimulator

This page outlines the repository branches and tags; what they are for, and our policy for what goes into it.

Also read
* [[Submitting code to OpenSim|Submitting Code to OpenSim]]

== Branches ==

=== master ===

The master branch holds bleeding edge OpenSimulator development.

'''OpenSimulator Master Branch Policies'''

* Master is not guaranteed to function. It might be in the middle of a transition, or undergoing a major overhaul.
* Master should always build
* All tests should run green on trunk
* Code should have been reasonably tested

'''Browse the master branch'''

* [http://opensimulator.org/viewgit/?a=tree&p=opensim&h=refs/heads/master OpenSimulator master branch]

=== New major Releases ===

A new release is created for main master code. 
* A tag with the full release version is added. (example 0.9.1.1). 
* A Branch named as the release number is created. 
* Master version is changed to at least the next minor number. 

=== New minor Releases ===

Minor releases will contain small changes or fixes to previous release. 
In many cases master branch does correspond to the required release in this case it is just like a new release 
On occasions it may be required to only include selected commits or even unique special code, in this case:
* change (checkout) to the branch of release to be fixed (or tag on main)
* Increment its minor version number(s).
* Create a new branch named as that version.
* do the fixes
* release

=== Release Candidates ===
Release candidates should be just snapshots of main code 
except any special reason, they may have at most a TAG on it 

=== Old procedure ( prior to 0.9x) ===

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

=== Other Branches ===

Other branches mainly contain temporary development work, for example to develop new code without disturb current master

'''Browse a list of all branches'''

* [http://opensimulator.org/viewgit/?a=summary&p=opensim List of Branches (see bottom of page)]

== Tags ==

Tags were originally used to trigger the automatic release build process. When it was time for a release, a <version>-release tag was applied to a branch, triggering the automated process that produced the release tarballs. For more details see [[Automated Release Building]]. Tags continue to be used to mark releases but may also be used for other purposes.

'''Browse a list of all tags'''

* [http://opensimulator.org/viewgit/?a=tags&p=opensim List of all tags]

← Older revision		Revision as of 08:15, 2 December 2023
Line 1:		Line 1:
−	{{Quicklinks\|~~Download~~}}{{ReleaseInfo}}	+	{{Quicklinks\|Branches}}{{ReleaseInfo}}

	== Zweige und Tags im Git Repo ==		== Zweige und Tags im Git Repo ==

@@ Line 1: / Line 1: @@
-__NOTOC__
+{{Quicklinks|Download}}{{ReleaseInfo}}
 {{Quicklinks}}
 == Zweige und Tags im Git Repo ==
@@ Line 92: / Line 91: @@
 * [http://opensimulator.org/viewgit/?a=tags&p=opensim List of all tags]

@@ Line 27: / Line 27: @@
 === master ===
-The master branch holds bleeding edge OpenSimulator development.
+Der Master-Zweig verfügt über die neueste OpenSimulator-Entwicklung.
-'''OpenSimulator Master Branch Policies'''
+'''OpenSimulator Master Branch Richtlinien'''
 * Master is not guaranteed to function. It might be in the middle of a transition, or undergoing a major overhaul.
@@ Line 36: / Line 36: @@
 * Code should have been reasonably tested
-'''Browse the master branch'''
+* Es kann nicht garantiert werden, dass der Master funktioniert. Möglicherweise befindet es sich mitten in einer Umstellung oder in einer umfassenden Überarbeitung.
 * [http://opensimulator.org/viewgit/?a=tree&p=opensim&h=refs/heads/master OpenSimulator master branch]
-=== New major Releases ===
+=== Neue Hauptveröffentlichungen ===
-A new release is created for main master code.<br>
+Für den Hauptmastercode wird ein neues Release erstellt.<br>
-* A tag with the full release version is added. (example 0.9.1.1).<br>
+* Ein Tag mit der Vollversion wird hinzugefügt. (Beispiel 0.9.1.1).
-* A Branch named as the release number is created.<br>
+* Es wird ein Branch mit dem Namen der Release-Nummer erstellt.
-* Master version is changed to at least the next minor number.<br>
+* Die Master-Version wird mindestens auf die nächste Minor-Nummer geändert.
-Minor releases will contain small changes or fixes to previous release.<br>
+=== Neue Nebenveröffentlichungen ===
-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:
+Nebenversionen enthalten kleine Änderungen oder Korrekturen gegenüber der vorherigen Version.<br>
-* change (checkout) to the branch of release to be fixed (or tag on main)
+In vielen Fällen entspricht der Master-Zweig der erforderlichen Version. In diesem Fall handelt es sich lediglich um eine neue Version.<br>
-* Increment its minor version number(s).
+Gelegentlich kann es erforderlich sein, nur ausgewählte Commits oder sogar einzigartigen Spezialcode einzuschließen, in diesem Fall:
-* Create a new branch named as that version.
-* do the fixes
+* Wechsel (Auschecken) zum Zweig des Releases, der repariert werden soll (oder Tag im Hauptzweig)
 * release
-=== Release Candidates ===
+=== Kandidaten freigeben ===
-Release candidates should be just snapshots of main code<br>
-except any special reason, they may have at most a TAG on it<br>
+Release-Kandidaten sollten, außer aus besonderen Gründen, lediglich Schnappschüsse des Hauptcodes sein sie dürfen höchstens einen TAG enthalten.
-=== Old procedure ( prior to 0.9x) ===
+=== Altes Verfahren (vor Version 0,9x) ===
-Old procedure used extra names like '-Release' and '-postfixes' after the version name.<br>
+Bei der alten Prozedur wurden nach dem Versionsnamen zusätzliche Namen wie „-Release“ und „-postfixes“ verwendet.<br>
-All releases should have their own version number.<br>
+Alle Veröffentlichungen sollten eine eigene Versionsnummer haben.<br>
-Lower digits of a version name are clear and enough identification for minor changes and bug fixes<br>
+Die unteren Ziffern eines Versionsnamens sind klar und bieten eine ausreichende Identifizierung für kleinere Änderungen und Fehlerbehebungen.<br>
-Something like  0.7.0.1-Release and 0.7.0.1-post-fixes was just redundant and confusing<br>
+So etwas wie 0.7.0.1-Release und 0.7.0.1-Post-Fixes war einfach überflüssig und verwirrend.<br>
-Under new format this would be just 0.7.0.1 and 0.7.0.2<br>
+Im neuen Format wären dies nur 0.7.0.1 und 0.7. 0,2<br>
 === Other Branches ===
-Other branches mainly contain temporary development work, for example to develop new code without disturb current master
+Andere Zweige enthalten hauptsächlich temporäre Entwicklungsarbeiten, beispielsweise um neuen Code zu entwickeln, ohne den aktuellen Master zu stören
-'''Browse a list of all branches'''
+'''Durchsuchen Sie eine Liste aller Filialen'''
-* [http://opensimulator.org/viewgit/?a=summary&p=opensim List of Branches (see bottom of page)]
+* [http://opensimulator.org/viewgit/?a=summary&p=opensim List of Branches (siehe unten auf der Seite)]
 == Tags ==

@@ Line 87: / Line 87: @@
 == Tags ==
-Tags were originally used to trigger the automatic release build process. When it was time for a release, a <version>-release tag was applied to a branch, triggering the automated process that produced the release tarballs. For more details see [[Automated Release Building]]. Tags continue to be used to mark releases but may also be used for other purposes.
+Ursprünglich wurden Tags verwendet, um den automatischen Release-Erstellungsprozess auszulösen. Als es Zeit für eine Veröffentlichung war, wurde ein <version>-release-Tag auf einen Zweig angewendet, wodurch der automatisierte Prozess ausgelöst wurde, der die Release-Tarballs erstellte. Weitere Einzelheiten finden Sie unter Automatisierte Release-Erstellung . Tags werden weiterhin zur Kennzeichnung von Veröffentlichungen verwendet, können aber auch für andere Zwecke verwendet werden.
-'''Browse a list of all tags'''
+'''Durchsuchen Sie eine Liste aller Tags'''
 * [http://opensimulator.org/viewgit/?a=tags&p=opensim List of all tags]

@@ Line 2: / Line 2: @@
 {{Quicklinks}}
-== Branches and Tags in the Git Repo ==
+== Zweige und Tags im Git Repo ==
-OpenSimulator uses Git for its source code repository. The repository contains various branches and tags used to identify development branches and release branches of the code. The primary git repository is hosted on the opensimulator.org domain. A mirror is maintained on Github. The Github repo is sync'ed with the primary every 10 minutes.
+OpenSimulator verwendet Git für sein Quellcode-Repository. Das Repository enthält verschiedene Zweige und Tags, die zur Identifizierung von Entwicklungszweigen und Releasezweigen des Codes verwendet werden. Das primäre Git-Repository wird auf der Domäne opensimulator.org gehostet. Auf Github wird ein Spiegel gepflegt. Das Github-Repo wird alle 10 Minuten mit dem primären Repo synchronisiert.
 === Git Repos ===
@@ Line 11: / Line 11: @@
 * [https://github.com/opensim/ '''Mirror''' OpenSimulator Github Repo]
 * [https://bitbucket.org/opensimulator/opensim/src/master/ '''Mirror''' OpenSimulator Bitbucket Repo]
-* [https://bitbucket.org/opensimulator/libopenmetaverse/src/master/ libOpenMetaverse for OpenSimulator] - our fork of libOpenMetaverse
+* [https://bitbucket.org/opensimulator/libopenmetaverse/src/master/ libOpenMetaverse for OpenSimulator] – unser Fork von libOpenMetaverse
-=== Repositories in the Primary Git ===
+=== Repositorys im primären Git ===
-* [http://opensimulator.org/viewgit/?a=summary&p=opensim opensim] - the OpenSimulator source code
+* [http://opensimulator.org/viewgit/?a=summary&p=opensim opensim] – der OpenSimulator Quellcode
-* [http://opensimulator.org/viewgit/?a=tree&p=opensim-libs opensim-libs] - forks of third party libraries used in building OpenSimulator
+* [http://opensimulator.org/viewgit/?a=tree&p=opensim-libs opensim-libs] – Zweige von Bibliotheken Dritter, die beim Erstellen von OpenSimulator verwendet werden
-This page outlines the repository branches and tags; what they are for, and our policy for what goes into it.
+Auf dieser Seite werden die Zweige und Tags des Repositorys beschrieben. wofür sie gedacht sind, und unsere Richtlinien für das, was darin enthalten ist.
-Also read
+Lesen Sie auch
-* [[Submitting code to OpenSim|Submitting Code to OpenSim]]
+* [[Submitting code to OpenSim|Senden von Code an OpenSim]]
 == Branches ==