Development/Git: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(A review of my changes required!)
Line 1: Line 1:
Development on the [[MusicBrainz Server]] source code is coordinated using [http://git-scm.com/ Git]. The Git web interface, http://git.musicbrainz.org, provides access to viewing the various repositories and even [http://git.musicbrainz.org/gitweb/?p=musicbrainz-server/core.git;a=tree browsing the source code].
This page describes how to use the MusicBrainz Git repository.

== Introduction ==

The latest stable and development versions of MusicBrainz Server are hosted on Git, at [http://git.musicbrainz.org git.musicbrainz.org]. You can browse the code through the web interface, and also clone each of these repositories for read only access. All releases we make are tagged on the master tree, and you can clone these to run stable released versions of MusicBrainz.


== Checking out source code ==
== Checking out source code ==
To check out source code from our repository use this command:
To create a local read only copy of the source code, clone a repository using this command:


git clone git://git.musicbrainz.org/musicbrainz-server/core.git mb_server
git clone git://git.musicbrainz.org/musicbrainz-server/core.git mb_server


And to stay up to date with the latest changes use:
This will clone the latest master branch -- see the README for more information.

To stay up to date with late changes, just use git pull like so:


git pull
git pull


The above will clone the latest master branch -- see the [http://git.musicbrainz.org/gitweb/?p=musicbrainz-server/core.git;a=blob;f=README;h=69eddf403c338eebc52066c7a676e2109ba4b3e6;hb=HEAD README] for more information. Alternatively, all official releases we make are tagged on the master tree, and these can be cloned to run a stable version of the [[MusicBrainz Server]].
== Help ==


Confused? Send an email to support@musicbrainz.org if you need more help, or drop by the [[IRC|IRC channel]]. Additionally, check out the [[Contact Us]] page for more ways to get in touch.
If you need help or are confused send an email to [mailto:support@musicbrainz.org support@musicbrainz.org], or drop by the [http://webchat.freenode.net/?channels=musicbrainz #musicbrainz IRC channel].


== Development with Git ==
== Development with Git ==
Line 28: Line 22:
git checkout -b my-cool-feature master
git checkout -b my-cool-feature master


When you are ready to share your work with us you have a few options - if you wish to submit a patches, you should use [http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html git format-patch]. These can then be emailed to the [[Developers Mailing List|developers mailing list]]. If you're doing work on more than one branch, or you'd like to have more control we are happy to give you a branch or repository on [http://git.musicbrainz.org git.musicbrainz.org] to push work to. For more information on this, please ask the list and someone will give you more details.
When you are ready to share your work with us you have a few options - if you wish to submit a patches, you should use [http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html git format-patch]. These can then be emailed to the [[Developers Mailing List|developers mailing list]]. If you're doing work on more than one branch, or you'd like to have more control, we are happy to give you a branch or repository on [http://git.musicbrainz.org git.musicbrainz.org] to push work to. For more information on this, please ask on the [[Developers Mailing List|developers mailing list]] and someone will give you more details.


== Git Resources ==
== Git Resources ==
Line 38: Line 32:
* [http://www.spheredev.org/wiki/Git_for_the_lazy Git for the lazy]
* [http://www.spheredev.org/wiki/Git_for_the_lazy Git for the lazy]
* [http://www.gnome.org/~newren/eg/ Easy Git (eg)]
* [http://www.gnome.org/~newren/eg/ Easy Git (eg)]

[[Category:Development]] [[Category:Server]]
[[Category:Development]] [[Category:Server]]

Revision as of 08:05, 9 February 2010

Development on the MusicBrainz Server source code is coordinated using Git. The Git web interface, http://git.musicbrainz.org, provides access to viewing the various repositories and even browsing the source code.

Checking out source code

To create a local read only copy of the source code, clone a repository using this command:

git clone git://git.musicbrainz.org/musicbrainz-server/core.git mb_server

And to stay up to date with the latest changes use:

git pull

The above will clone the latest master branch -- see the README for more information. Alternatively, all official releases we make are tagged on the master tree, and these can be cloned to run a stable version of the MusicBrainz Server.

If you need help or are confused send an email to support@musicbrainz.org, or drop by the #musicbrainz IRC channel.

Development with Git

If you want to help contribute to MusicBrainz - it's really simple! All you need to do is branch off master and commit there:

git clone git://git.musicbrainz.org/musicbrainz-server/core.git mb_server
cd mb_server
git checkout -b my-cool-feature master

When you are ready to share your work with us you have a few options - if you wish to submit a patches, you should use git format-patch. These can then be emailed to the developers mailing list. If you're doing work on more than one branch, or you'd like to have more control, we are happy to give you a branch or repository on git.musicbrainz.org to push work to. For more information on this, please ask on the developers mailing list and someone will give you more details.

Git Resources

If you're new to Git, don't worry - there is plenty of excellent documentation about how to use it: