I don't like the rc1 tag. The date tag is more descriptive. and easier to automate. As for the tag being or not in git doesn't really matter. I used to rename the released branch to GA-4.4.x after the vote and leave the tag on there as well. In the end it is the commit-id that is significnant.
On Thu, Nov 5, 2015 at 9:52 AM, Remi Bergsma <rberg...@schubergphilis.com> wrote: > Guys, > > I accidentally pushed the 4.6.0 tag and I shouldn't have done that before > it is final. Sorry! > > Let's see if we can get rid of it until the vote passes. > > Regards, Remi > > Sent from my iPhone > > > On 05 Nov 2015, at 09:35, Rene Moser <m...@renemoser.net> wrote: > > > > Hi > > > > I have kind of a question about the tagging policy in cloudstack git > repo: > > > > We now have tag 4.6.0 but we call it an RC. This raises 2 problems: > > > > 1st: from the public perspective, this is a released version. Or how can > > anyone not related to the project see, if this is an RC or not? > > > > 2nd: tags seems not to be persistent. If we decide to do another RC, the > > tag would be moved to another commit. If we test "4.6.0" we can not say > > which version has been tested. > > > > Proposal: We adopt the well known versioning model "semantic versioning" > > http://semver.org/. > > > > This means the RC would have been named 4.6.0-RC20151104T1522 or > 4.6.0-rc.1 > > > > Do I miss anything? Any thoughts? > > > > Regards > > René > -- Daan
