flume-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hshreedha...@apache.org
Subject svn commit: r1377110 - /flume/site/trunk/content/sphinx/source.rst
Date Fri, 24 Aug 2012 20:59:43 GMT
Author: hshreedharan
Date: Fri Aug 24 20:59:43 2012
New Revision: 1377110

URL: http://svn.apache.org/viewvc?rev=1377110&view=rev
Log:
Making some clarification on the release branches.

(Hari Shreedharan)


Modified:
    flume/site/trunk/content/sphinx/source.rst

Modified: flume/site/trunk/content/sphinx/source.rst
URL: http://svn.apache.org/viewvc/flume/site/trunk/content/sphinx/source.rst?rev=1377110&r1=1377109&r2=1377110&view=diff
==============================================================================
--- flume/site/trunk/content/sphinx/source.rst (original)
+++ flume/site/trunk/content/sphinx/source.rst Fri Aug 24 20:59:43 2012
@@ -63,7 +63,8 @@ When a release is finalized, the current
 branched off the current release branch. The new branch will represent the next release and
all commits not meant for the current release must
 go to the new branch once the current branch is frozen. The release manager then pushes release
related commits to the current branch.
 
-For example, if the next release is flume-1.3.0, and it is finalized, the release manager
will create a new branch, say flume-1.4.0 from the latest commit of 
+For example, if the next release is flume-1.3.0, all commits should go to trunk and flume-1.3.0.
+When the release is finalized, the release manager will create a new branch, say flume-1.4.0
from the latest commit of 
 flume-1.3.0. All further non-release related commits should go to trunk and flume-1.4.0 (unless
the release manager thinks otherwise - in which case it can
 go to flume-1.3.0 and flume-1.4.0). 
 



Mime
View raw message