Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Mon, 21 Nov 2011 09:39:16 -0000
Message-ID: <20111121093916.83514.47448@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Trivial_Update_of_=22Git=5FAt=5FApache=5FGui?=
 =?utf-8?q?de=22_by_ChristianGrobmeier?=
Auto-Submitted: auto-generated

Dear Wiki user,

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

The "Git_At_Apache_Guide" page has been changed by ChristianGrobmeier:
http://wiki.apache.org/couchdb/Git_At_Apache_Guide?action=3Ddiff&rev1=3D29&=
rev2=3D30

Comment:
comment and link to release procedure added

   1. git-rebase, git-stash and stashing via git-merge --interactive is onl=
y 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?''
+ =

+ =

  =3D=3D Non-ASF repository collaboration =3D=3D
   1. Doing a test feature branch in private or in a forked github reposito=
ry is perfectly fine. But committers should push to the canonical ASF repos=
itory early and often to prevent a fragmentation of the community developme=
nt effort.
   1. Even if GIT supports the additional author information, the establish=
ed policy that committers should apply their commits to the canonical repos=
itory themself remains intact.
@@ -39, +42 @@

   1. The project documentation and project site shall mention the apache.o=
rg based GIT repo as the canonical source location.
  =

  =3D=3D Cutting Releases with GIT =3D=3D
+ =

+ The release plan from couchdb can be found here: http://wiki.apache.org/c=
ouchdb/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.