Thanks for all the input. So the bottom line is, we only need the passed tag to be preserved as 3.0.0-incubating version. I'll delete the unnecessary tags.
Thanks. On Thu, Nov 14, 2013 at 8:37 PM, Chip Childers <[email protected]>wrote: > On Thu, Nov 14, 2013 at 03:13:25PM +0100, Noah Slater wrote: > > Lahiru, > > > > The way we solve this on CouchDB is to only tag once the vote passes. > > > > So, we can have an rc1, rc2, and rc3. But only once rc3 passes, do we > > tag it as 3.0.0, or whatever. > > > > There's really no practical need to tag before the vote passes. > > > > Let me know if you have any other questions. > > +1 to what Noah said above. As an alternative, in CloudStack, the > release script tags the RM's local repo during the process of generating > the source artifacts with a proper release number tag (clearly indicating > the specific release number, not the RC), but it is not pushed upstream to > the ASF repo until the VOTE passes. > -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: [email protected] cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
