Use Advanced Search to search the entire archive.
[jsr363-experts] Re: Feature Freeze before Final Draft
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: Feature Freeze before Final Draft
- Date: Wed, 22 Jun 2016 15:03:08 +0200
All,
Have you thought about a reasonable duration of the Proposed Final Draft? I
mentioned JSR 330 used just a week (under special circumstances but that
means, the JCP has no strict minimal duration, every JSR decides how long
till it wishes to do a Final approval ballot, for 354 is was roughly 2
months)
Leo suggested to wait at least 3 months, till after JavaOne.
I consider it a risk and probably a bit long because
- The API is fairly stable, not just since 2014, some elements were shaped
for at least 6 years including the Open Source ecosystem or 275 work. At
most people found bugs or improvements to the RI, that may happen at
JavaOne or later, if it's significant, we'll offer a MR or patch release,
also see JSR 354 and others
- There are very few ballots now, including many EE 8 Renewal Ballots (or
even things like Jigsaw if they don't show progress;-) from October on we
expect to see nearly a dozen, so PMO and everyone else will be much busier
then
- Should the Oracle vs. Java EE situation escalate to the worst extent,
then "fallout" such as some members no longer voting at all or voting "No"
on everything could be possible. We saw that with Apache and others between
2007 and their withdrawal from the EC. For some this might seem an option
again and even non-Oracle JSRs could be entangled in such "Civil War";-O
Do you have a suggestion for the number of weeks if Harold/PMO asks us?
Thanks and Regards,
Werner