X-Git-Url: http://git.i-scream.org/?a=blobdiff_plain;f=www%2Fgit.xhtml;fp=www%2Fgit.xhtml;h=f509257f02254ecf7f2dccdbe950cd2e2b509792;hb=067b15fa441dd518e49511ae3080d5814b6e8357;hp=a2227f2380a1017a85a6be18c193e185b67d9a85;hpb=d600a03122e2387ac3117a082dc2995e1f39c15f;p=www.i-scream.org.git diff --git a/www/git.xhtml b/www/git.xhtml index a2227f2..f509257 100644 --- a/www/git.xhtml +++ b/www/git.xhtml @@ -75,6 +75,48 @@ git clone ssh://git@git.i-scream.org/libstatgrab

http://github.com/i-scream

+

+ Git guidelines +

+

+ We've chosen a set of guidelines to work by so that + everybody is clear about how the Git repositories will be + used. This should make life easier for developers and + users. The aim is to keep things clear and simple without + adding unnecessary overheads. We don't have need for + anything as complex as git-flow. +

+
    +
  1. + The master branch will always be buildable + and should be usable. Development work does not happen + here directly. +
  2. +
  3. + New releases will be taken from the master + branch and will be tagged there. +
  4. +
  5. + The master branch will never have its history rewritten. +
  6. +
  7. + Development work will be done on branches. These + branches may only live for the period of the development + work. Once the work is complete and tested it will be + merged to master and the branch may be deleted. +
  8. +
  9. + The history on development branches may be rewritten to + tidy things up before merging. This probably won't + happen often, but don't get upset if it does. +
  10. +
  11. + If you want to submit changes it's best to do them + against the master branch unless you're + specifically working with a developer on an issue + already. +
  12. +