[7u communication] Schedule and release renumbering update

[Ismael Juma]

On Wed, Apr 24, 2013 at 9:48 AM, Andrew Hughes <gnu.andrew at 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.

Best,
Ismael