Accelerating the JDK release cadence
peter.lawrey at gmail.com
Wed Sep 13 18:20:37 UTC 2017
This reminds me of the Ubuntu version numbers which I don't mind at all.
Note: the $MONTH is always 2 digits which has a nice symmetry as "yy'.'MM".
If we avoid releasing after September each year, one digit should be fine.
On 13 September 2017 at 17:59, <mark.reinhold at oracle.com> wrote:
> 2017/9/13 9:55:34 -0700, aph at redhat.com:
> > On 13/09/17 15:25, Brian Goetz wrote:
> >> Platform JSR for 18.3 posted yesterday:
> >> https://jcp.org/en/jsr/detail?id=383
> >> Now in review, to be followed by ballot, in accordance with JCP process,
> >> as usual.
> >> Component JSRs will come in as they always have; through the appropriate
> >> platform (umbrella) JSRs.
> > But why the blinking flip is it called 18.3? I've looked in a few
> emails but I
> > get so many, I may have missed the explanation.
> From my blog entry (https://mreinhold.org/blog/forward-faster):
> To make it clear that these are time-based releases, and to make it
> easy to figure out the release date of any particular release, the
> version strings of feature releases will be of the form `$YEAR.$MONTH`.
> Thus next year's March release will be 18.3, and the September
> long-term support release will be 18.9.
> That's the proposal. I'm sure there will be further discussion, but in
> the meantime we had to pick some number to use on the JSR submission, so
> it's "18.3".
> - Mark
More information about the discuss