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 "Merge_Procedure" by NoahSlater
Date Thu, 25 Apr 2013 19:54:19 GMT
Dear Wiki user,

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

The "Merge_Procedure" page has been changed by NoahSlater:
http://wiki.apache.org/couchdb/Merge_Procedure?action=diff&rev1=13&rev2=14

  
  A feature branch should consist of the smallest number of meaningful commits as possible.
For bug fixes and small features, this is likely to be a single commit. For larger changes,
multiple commits might be necessary. The guiding principle for deciding how many commits is
coherence. A commit should be readable and, ideally, implement one distinct idea. A feature
that requires multiple enhancements to achieve its goal should be presented as multiple commits.
It is *not* necessary for the system to pass the test suite for any subset of these commits,
only their combination.
  
- '''@@ BOB, PLEASE CREATE A LIST OF INSTRUCTIONS, INCLUDING COPY AND PASTE GIT COMMANDS,
HERE.'''
- 
  = Merge Request =
  
  The merge request is done by the developer wanting to add changes to a release branch.
@@ -65, +63 @@

  
   * Run `make distcheck` a few times and verify that it works reliably.
  
-  * Send an email to [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list. [[http://wiki.apache.org/couchdb/Merge_Request#preview | You can use this template]].
+  * Send an email to [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list. [[http://wiki.apache.org/couchdb/Merge_Request#preview | You can use this template]].
'''@@ Create template in couchdb-admin'''
  
     * Choose a subject like "[MERGE] Feature description"
  

Mime
View raw message