Le 28/12/15 02:12, Zheng, Kai a écrit :
> Hi,
>
> I'd suggest we use 'trunk' instead of 'master' to name the trunk branch as 
> mostly often seen in other projects. 

+1 to that.

> It will be easier understood by new comers.
> Meanwhile, I'll update pom.xml files to use the version like '2.0.0-SNAPSHOT' 
> for the trunk branch, 
Keep it to 1.0.0-RC2-SNAPSHOT. this is what is going to be released.

> and create a branch like 'branch-1.0.0-RC2' using the current version 
> '1.0.0-RC2-SNAPSHOT' for the upcoming release. 

Don't. It's done automatically when we cut the release.

> I thought every release should cut its own branch, though unfortunately we 
> don't have one for the past RC1 release.
of cpurse we have one :
https://git1-us-west.apache.org/repos/asf?p=directory-kerby.git;a=tag;h=4bea5b4979eab53e090bf051a25d1fb017512c55
>
> If no objection, I'll proceed today late. And after that, I'll do some 
> cleanup and move some codes out of the 'branch-1.0.0-RC2' branch to prepare 
> for the release.
The release process will take charge of taht automatically. There is
nothing you need to do, exept may be change from master to trunk.

Reply via email to