----- Original Message ----- > On Wed, Apr 24, 2013 at 9:48 AM, Andrew Hughes <gnu.and...@redhat.com>wrote: > > > With IcedTea, we avoid this by using micro numbering for security > > releases. So the > > next feature release is always the next minor number bump and the next > > new Java > > specification level is always the next major number bump e.g. > > > > 2.x.x - related to OpenJDK 7. > > 2.3.x - original u6 feature release and all subsequent security releases > > on top > > 2.4.x - next feature release (u40 now) > > 3.x.x - related to OpenJDK 8. > > > > This is the right way of doing it as far as I am concerned, but it's > probably not possible to make this change in the JDK 7 train without > breaking something. Maybe something to consider for JDK 8 though. >
Yeah, I guess there's a lot of things that will break by changing versioning. I'm never really followed the proprietary releases, so it's not a system I've been aware of until 7u. > Best, > Ismael > Thanks, -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
