Repository: commons-math
Updated Branches:
  refs/heads/master 6ddd71b06 -> d9e43edd1

chore: adding tagging comments to development.howto


Branch: refs/heads/master
Commit: d9e43edd13d55224fabc9a65b75884a77a3d56b7
Parents: 6ddd71b
Author: Rob Tompkins <>
Authored: Tue Sep 20 14:20:27 2016 -0400
Committer: Rob Tompkins <>
Committed: Tue Sep 20 14:20:27 2016 -0400

 doc/development/development.howto.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/development/development.howto.txt 
index 7b5ec93..525ce2f 100644
--- a/doc/development/development.howto.txt
+++ b/doc/development/development.howto.txt
@@ -5,9 +5,9 @@ This document summarizes a discussion that took place on the 
"dev" ML:
 The conclusions reported here are based on ideas presented in this blog post:
-1. The "master" branch can only contain released code; i.e. the only
-   accepted commits are the result of a merge from the "release" branch
-   (from a release candidate that passed a vote).
+1. A tag in git will represent a full release (from a release candidate that
+   passed a vote). Note, this tag will not have the suffix "RC#", as tags
+   with that suffix represent a release candidate.
 2. Contents that is candidate for being released must be merged into the
    "release" branch, from the "master" branch.
 3. The "master" branch collects all modifications that will be part

Reply via email to