That's what the tag is for On Mon, Nov 9, 2015 at 2:03 PM, Fengdong Yu <[email protected]> wrote:
> One branch take care only one release. then create a new branch for next > release. > > Don’t make branch-0.5 to take care 0.5.x release. that’s not make sense. > > because if I want to get 0.5.3 source code after 0.5.5 released. It’s > very trouble to get it. > > > > > > On Nov 9, 2015, at 12:31 PM, moon soo Lee <[email protected]> wrote: > > > > It was intended to branch-0.5 take care all 0.5.x release with tag. > > Only reason branch-0.5.5 is created for 0.5.5 instead of using branch-0.5 > > since we decided to release 0.5.5 from master after it diverged a lot. > > > > So, I expect from 0.6.x we use single branch, branch-0.6 for all 0.6.x > > release with tags. > > > > For branch-0.5.5, would it make sense to leave version name as > > 0.5.5-incubating-SNAPSHOT after release in the pom.xml files? > > > > Thanks, > > moon > > > > On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik <[email protected]> > wrote: > > > >> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote: > >>> > >>> Hi, > >>> > >>> All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is > >>> weird. branch name is 0.5.5, but the actually version is 0.5.6. > >>> > >>> A common proper way is create a new branch for 0.5.6 based on the > 0.5.5, > >>> then changed the version to 0.5.6 on the new branch. > >> > >> There're a few school of thoughts here: > >> - one, as you explained, where new branch is created for each release > >> - another, where the same branch is used for a series of the releases, > say > >> 0.5.x and each new release is simply tagged. > >> > >> Current situation with 0.5.5 is neither, because 0.5.5 isn't released > yet, > >> but > >> the branch version is already moved. Which might lead to all sorts of > the > >> confusions if more release candidates are needed. > >> > >> Cos > >> > >
