Thanks for the clarification. Doesnt this process make the release managers job harder by having to wade through all the commits on the development branch and cherry pick them? I think I will hold my commits until the release to make it easier. On Dec 26, 2014 1:00 PM, "Christopher" <ctubb...@apache.org> wrote:
> Changes for 1.6.3 should go in the 1.6 branch. However, it may be the case > that branch is released from an earlier commit. The release manager should > be responsible for ensuring any additional fixes included in the 1.6.2 > release from the 1.6 branch are properly marked for 1.6.2. > > > -- > Christopher L Tubbs II > http://gravatar.com/ctubbsii > > On Fri, Dec 26, 2014 at 12:46 PM, Dave Marion <dmario...@gmail.com> wrote: > > > That didnt clear it up for me. BTW, the release management section needs > to > > be changed now that we have adopted semver. I will make a ticket for > that. > > > > I will change the question. We are working on releasing 1.6.2. Where > should > > changes for 1.6.3 be placed? > > Dave, consult http://accumulo.apache.org/git.html > > > > tl;dr No, the 1.6 branch is for the lifetime of all 1.6 versions. > > > > WRT the other branches you are seeing, I'm guessing it's Corey doing > > something in preparation for making a 1.6.2. > > > > dlmar...@comcast.net wrote: > > > > > We have 1.6, 1.6.2-SNAPSHOT, and 1.6.2-rc0 branches. Should we change > the > > > version in the 1.6 branch to 1.6.3-SNAPSHOT? If not, what's the plan? > > > > > > > > >
