couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Couchdb Wiki] Update of "Git_At_Apache_Guide" by MarkStruberg
Date Fri, 18 Nov 2011 23:01:15 GMT
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 MarkStruberg:

  For understanding the technical aspects of GIT and SVN please read [[SVNvsGIT]]. This will
help you to grok the design decissions
  GIT at the ASF is currently an experiment. We have defined criterias under which this experiment
is being considered [[GitSuccessCriteria|successfull]]
  == Project Structure ==
   1. Each project can optionally have a separated PMC-private GIT repository which conains
confidential legal stuff like trademark contracts, creds for community accounts like twitter,
@@ -22, +20 @@

   1. It must not be possible to change the history of a project or delete certain branches.
Any sha1 in master or any productive branch must not be allowed to get changed!
   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. 
+  1. It must not be possible to delete release tags.
  == Social Aspects ==
   1. Pulling from some external (non hosted) repository must only happen if all
the respective commits are done by a person which has an iCLA on file.
   1. Incorporating changes from other contributors (no iCLA on file) must only be handled
via JIRA attached patches because of legal reasons (the 'grant inclusion under ALv2' flag
in JIRA).
+  1. The project documentation and project site shall mention the based GIT repo
as the canonical source location.
  == Cutting Releases with GIT ==
  Apache Maven supports the usage of GIT with the [[|maven-scm-providers-git]]
since 2008.

View raw message