[Couchdb Wiki] Trivial Update of "Git_At_Apache_Guide" by ChristianGrobmeier

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "Git_At_Apache_Guide" page has been changed by ChristianGrobmeier:
http://wiki.apache.org/couchdb/Git_At_Apache_Guide?action=diff&rev1=29&rev2=30

Comment:
comment and link to release procedure added

   1. git-rebase, git-stash and stashing via git-merge --interactive is only allowed if the history of external contributions remains preserved.
   1. It must not be possible to delete release tags.
  
+ ''grobmeier: deleting tags is possible with SVN, for example when the RC1 tag has failed the vote. Why isn't it allowed with git?''
+ 
+ 
  == Non-ASF repository collaboration ==
   1. Doing a test feature branch in private or in a forked github repository is perfectly fine. But committers should push to the canonical ASF repository early and often to prevent a fragmentation of the community development effort.
   1. Even if GIT supports the additional author information, the established policy that committers should apply their commits to the canonical repository themself remains intact.
@@ -39, +42 @@

   1. The project documentation and project site shall mention the apache.org based GIT repo as the canonical source location.
  
  == Cutting Releases with GIT ==
+ 
+ The release plan from couchdb can be found here: http://wiki.apache.org/couchdb/Release_procedure
+ 
  Apache Maven supports the usage of GIT with the [[http://maven.apache.org/scm/git.html|maven-scm-providers-git]] since 2008.
  
  Be aware that the branch created by a release with GIT always covers the whole repository.