Re: spring2 release number mess

On 01/09/2012 04:00 PM, Ralph Apel wrote:
> afaik 2.5.6 is the (upstream) version number and SEC01 SEC02 SEC03 are
> some kind of release additives.

It's a security patch added *after* 2.5.6 went final.

> Out policy at JPP has from the beginning been
> 
> %{version}-0.%{additive}.N
> 
> where the N is our count of our builds of upstreams
> %{version}-%{additive}
> 
> The last release WAS 2.5.6-6.SEC01
> and SHOULD HAVE BEEN 2.5.6-0.SEC01.6
> 
> Then an upgrade to 2.5.6-0.SEC03.1 wouldn't have been a problem.

For pre-releases, maybe. This is not a pre-release, but a post release.
Spring 2.5.6 was already final which is one reason why it had a Release > 0.

I still don't see why it can't be 2.5.6, 2.5.6.SEC01, 2.5.6.SEC02, ...
(this works fine, doesn't it?).

The last release was 2.5.6-6.SEC01 because the prior Release was 5 (and
had gone through 1, 2, 3, and 4, presumably). Spring 2.5.6 is final.
What else could the Release have been in this case?