This is an old revision of the document!
Within the X2go project development code is shared via a public GIT repository hosted by DAS-NETZWERKTEAM in Kiel, Nothern Germany (Servers: Hetzner Online AG). For any X2go GIT related questions, please contact our GIT repository administrator (currently: Mike Gabriel): git-admin (at) x2go (dot) org
.
Browse the X2go GIT repository tree in a webbrowser:
http://code.x2go.org/gitweb
Anonymous X2go GIT Repository Access via git:// protocol (read-only)
The X2go project's BerliOS Developer GIT repository can be checked out through anonymous GIT with the following instruction set (in a Unix-like console session).
$ mkdir -p ~/x2go $ cd ~/x2go $ git clone git://code.x2go.org/x2go/all-packages .
Contributing to X2go*
Only project developers can access the GIT tree via the SSH method. Please understand that we only restrictively grant write access to our GIT repository. However, you can send us patches via Mail (git-send-email). For submitting X2go patches, please use this eMail address:
patches@x2go.org
Developer GIT Access via SSH
As an X2go developer, please substitute the field <developername> in the text below with your account login name. Substitute <package> with the X2go source package that you want to work on, substitute <branch> with the name of the branch of <package> you are contributing to. Enter your code.x2go.org Git site password when prompted.
$ cd ~/x2go/<package> $ git push ssh://<developername>@code.x2go.org/srv/git/code.x2go.org/<package> <branch>
SSH Key Fingerprints of code.x2go.org (fqdn: ymir.das-netzwerkteam.de)
RSA Key: ab:cd:4b:b2:d1:d1:19:11:ed:24:83:5a:06:b1:d4:d3
On each GIT repositories (one GIT per source package) there are 2 permanent branches:
An X2go release always means a merge from the develop branch to the master branch that then gets tagged with the upstream version number.
All X2go components that have been accepted for a future release can be found in the develop branch
There can be different temporary branches around release management:
And there can be different temporary branches around feature development. These branches we call feature branches:
Further policies are: