On Sat, Jun 09, 2012 at 10:44:23AM -0600, Leif Hedstrom wrote:
> >
> > On a related note.. it would be nice if the release candidates could be
> > tagged as release candidates (trafficserver-3.x.y-rc1), instead of having
> > several versions of trafficserver-3.x.y.tar.gz floating around.
>
> So that would then also be the final release name name (e.g.
> trafficsever-3.3.0-rc1-dev)? I find that somewhat confusing,
I agree, that looks ugly. I was mainly thinking about stable releaes.
> If we are concerned about the reuse of the minor number during dev
> release recycles, I'd suggest we do what Nick proposed, and simply
> skip version numbers.
It's not skipping, it's bumping. The first 3.1.4 would still have been
released, but it would be a brown paper bag release..
52bb0e0cfd595f48844e2463e3a531f19cf27ff9 would be 3.1.4
886465e5cbaaf41e6486da265bc0cc6ddbe23933 would be 3.1.5
> This has another problem though, which is that all Jira tickets have
> to be renumbered on a respin (at least I would insist that they
> should).
It's not a respin. Lots of tickets were closed on 3.1.4, and some more
on 3.1.5. If some user complains about problems with 3.1.4 it would be
possible to tell that this was fixed on v3.1.5, vs. the situatuin now
where there are two versions of 3.1.4 floating around, which are close
to impossible to tell apart (both look just as official, signed by the
same gpg-key).
But yes.. tickets targeted for the next release would have to be bumped.
-jf
