Use Advanced Search to search the entire archive.
[jsr363-experts] Re: Feature Freeze before Final Draft
- From: Leonardo Lima <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: Feature Freeze before Final Draft
- Date: Tue, 21 Jun 2016 11:03:48 -0500
Werner,
I think it should be best to have the JSR as "almost-final" (I believe
that'd be proposed final draft?) by JavaOne. That way, we can still gather
input in hackergartens and/or BoFs. We can have everything ready to file
for Final just after 1-2 weeks after J1.
Regards,
Leo.
On Tue, Jun 21, 2016 at 7:48 AM, Werner Keil
<
>
wrote:
>
Please also review the Spec Document again if you can.
>
The license paragraph exists for "Evaluation" and "Implementation". Only
>
when the Final version is approved and released both will go out to
>
separate download deliverables (see all major new JSRs that went final like
>
Money https://jcp.org/aboutJava/communityprocess/final/jsr354/index.html,
>
JCache, etc.)
>
>
For the Proposed Final Draft only the "Evaluation" part is relevant.
>
Aside from brushing up to SPI changes, I added another Use Case chapter on
>
DevOps and Cloud. Quite a hot topic and thanks to being picked up by
>
PCP/Parfait with the latest releases it is of course a good thing to
>
mention (aside from everyone staring at or rushing to the Cloud right now;-)
>
>
We aim for Code-freeze of the API and RI pretty much around June 30/July 1
>
(if there was any issue or significant input for changes we still have the
>
weekend)
>
July 4 is a holiday in the US, so PMO would not process anything before
>
the 5th, so around then looks good to submit it. Depending on how fast it's
>
put online, the community and EC members may see it before the EC call on
>
July 12th, but the Proposed Final Draft is just for review, no ballot there
>
yet. JSR 354 had its PFD on March 13 and Approval Ballot on April 28. Final
>
was out exactly 2 months later on May 13. Even if JavaOne was to snub and
>
ignore it again (unlike the Awards) or Oracle ended up with a "JDK
>
Personality Show" while the community looks for other forums like DevoXX,
>
etc. a Final date ideally before JavaOne looks best and looking at 354
>
doable.
>
There's a Creation Review for Java SE 9 Umbrella (actually right now) and
>
JSON-B has a Public Review Ballot at the end of July. So it could be best
>
to aim at a nearby date, otherwise there are not too many ballots anyway.
>
JSR 330 (Dependency Injection) showed, there seems almost no rule for a
>
minimum PFD duration. It went out on Sep 22 followed by the ballot starting
>
only a week later on Sep 29. I'd say at least 14 days could be good in our
>
case if asked, if you think we should take longer, please advise.
>
>
Cheers,
>
Werner
>