couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "GitSuccessCriteria" by JanLehnardt
Date Fri, 18 Nov 2011 22:00:28 GMT
Dear Wiki user,

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

The "GitSuccessCriteria" page has been changed by JanLehnardt:
http://wiki.apache.org/couchdb/GitSuccessCriteria?action=diff&rev1=5&rev2=6

Comment:
split criteria into technical and community

  = Criteria for GIT @ ASF =
  This list describes all points which should be met for GIT to become a SCM which can finally
be used for ASF projects which like to use GIT.
  
+  1. Technical
-  1. The preservation of the commit history must be guaranteed. It must be practically impossible
to delete any piece of commit history which made it into an official ASF release
+    1. The preservation of the commit history must be guaranteed. It must be practically
impossible to delete any piece of commit history which made it into an official ASF release
-  1. The commiter of any change must be authenticated. It must not be possible to fake the
committer id and thus taint the commit history.
+    1. The commiter of any change must be authenticated. It must not be possible to fake
the committer id and thus taint the commit history.
-  1. In cases where the committer is not the author, the committer must ensure that the author
has granted the code to the ASF under the terms of the [[http://www.apache.org/licenses/LICENSE-2.0|Apache
License]] or that the contribution is sufficiently trivial to waive this requirement.
+    1. In cases where the committer is not the author, the committer must ensure that the
author has granted the code to the ASF under the terms of the [[http://www.apache.org/licenses/LICENSE-2.0|Apache
License]] or that the contribution is sufficiently trivial to waive this requirement.
-  1. The single canonical project repository (repositories) must be hosted on ASF servers
under full control of the ASF infra team.
+    1. The single canonical project repository (repositories) must be hosted on ASF servers
under full control of the ASF infra team.
-  1. There must be no other legal problem because of the usage of GIT as canonical
+    1. There must be no other legal problem because of the usage of GIT as canonical
-  1. The canonical GIT repo hosted at the ASF must be the repo to cut official ASF releases
from.
+    1. The canonical GIT repo hosted at the ASF must be the repo to cut official ASF releases
from.
-  1. There must be backups from the repos.
+    1. There must be backups from the repos.
-  1. There must be no blocking technical issue left with GIT restricting the community
+    1. There must be no blocking technical issue left with GIT restricting the community
  
+  2. Community
+    1. Clear guidelines for committers on handling of development branches, feature branches,
release branches and maintenance branches.
+    1. Clear guidelines for committers on handling security@ issues.
+    1. Clear guidelines on how to cut releases from git.
+ 

Mime
View raw message