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 "Git_At_Apache_Guide" by JanLehnardt
Date Fri, 18 Nov 2011 20:26:57 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 JanLehnardt:
http://wiki.apache.org/couchdb/Git_At_Apache_Guide?action=diff&rev1=6&rev2=7

  For understanding the technical aspects of GIT and SVN please read [[SVNvsGIT]]. This will
help you to grok the design decissions
  
  == Project Structure ==
-  1. Each project should get one PMC-private GIT repository which conains confidential legal
stuff like trademark contracts, creds for community accounts like twitter, etc
+  1. Each project should have a way to share PMC-private code. This can be a separate repo
or just branches secured by naming convention (e.g. branches/private/...). It is for confidential
legal stuff like trademark contracts, creds for community accounts like twitter, etc
   1. Each project has at least one GIT repository which contains the main project and is
read/writable for all committers
   1. Some projects might need additional GIT repositories containing project parts which
have a completely separated lifecycle from the main project. This can be various build-tools
(checkstyle-rules, project specific maven-plugins which are needed to build the project) or
the project site. This is needed because a GIT branch and tag always affects the whole repository
  

Mime
View raw message