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: Fri, 30 Sep 2016 12:03:53 +0200
Martin,
Congrats, I saw, ACE has an SIS talk again this year.
I offered one related to Monitoring, but in the Big Data selection a
comparison of projects like Sirona to Parfait and other solutions did not
seem attractive enough (nothing on Sirona either in "Core", I am not in
that podling, but maybe the topic could have been more interesting there)
And the other proposal on Pluto 3 also was not so exciting. Anatole has a
talk on Tamaya again, that is still "en vogue" it seems despite some former
podling members constantly foul-mouthing about it and claiming "they have
the answer to configuration, life and everything" all alone ;-)
I was invited to speak at Java2Days in Sofia the same week, so I guess I'll
skip ApacheCon (Anatole asked others to join, but he did not propose me or
others as co-speakers, so I guess it would be hard, though maybe possible
to still add co-speakers, JavaOne did, that's how Leo and Otavio added me
to the final talk) but I may have a configuration talk at
Java2Days/Cloud2Days instead. Which also relates to JSR 363.
Any progress or news on a migration path for GeoAPI?
Regards,
Werner
On Fri, Jul 15, 2016 at 9:00 PM, Werner Keil
<
>
wrote:
>
Martin,
>
>
Thanks for those questions. The current state/stage of JSR 363 is
>
"Proposed Final Draft". From an API point (unless we or anybody else come
>
across a severe bug or issue) it should mean "Feature Freeze" and no
>
further renaming or refactoring of e.g. method signatures should now take
>
place between 0.9 and 1.0
>
All software artifacts will have a BSD-like (3-clause) license, we got
>
that recommended by more than just Eclipse and follow how every JSR (except
>
107 and 354 they were under the same impression as we about the API before
>
we fixed that) and the Spec License only applies to the written Spec
>
Document. No single software artifact like API, RI, TCK etc.
>
>
The specification in all revisions is under https://java.net/
>
projects/unitsofmeasurement/downloads. Until we learn that java.net was
>
completely shut down we trust in using the download section. Every file is
>
available to put on GitHub or elsewhere if necessary at a later point.
>
>
There was a minor misunderstanding about the exact Spec License for PFD. I
>
thought because the "Final Draft" in the name it would be the evaluation
>
form also used for 1.0 Final. It seems closer to the Public Draft, but
>
Harold asked for a few small tweaks in the wording. I sent the new
>
attachments and if he finds everything is in shape, Oracle/PMO should
>
publish the PFD within a few days (next week I assume) and Heather also
>
confirmed in the EC call that they're working on the PFD.
>
>
There is no strict deadline or period between PFD and Final (some JSRs
>
like 354 took around 2 months, others like JCache took up to 2 years before
>
Final was approved ;-) but given the relative maturity and hoping to go
>
Final before a frenzy of Java EE JSRs are subject to ballots (either way
>
but mostly Renewal Ballots I assume) the idea was to start a Final Approval
>
ballot within around 4-8 weeks after the PFD (so no later than JavaOneish
>
time probably early September at most)
>
>
Does that sound OK to you, also from a GeoAPI standpoint?
>
>
Parfait 0.4 just went GA with the Public Review 0.8 state of JSR 363.
>
That's a good reference, also briefly mentioned in the spec. If you feel
>
other use cases including GeoAPI should be mentioned, please feel free.
>
There's a bit of time and room for that, though it also has not changed
>
substantially since Public Review.
>
>
Regards,
>
Werner
>
>
>
On Fri, Jul 15, 2016 at 10:23 AM, Martin Desruisseaux <
>
>
>
wrote:
>
>
> Hello Werner
>
>
>
> Pardon my naive question, but would it be possible to remind me the
>
> current state of JSR-363? I got some questions on other mailing lists and
>
> would like to verify my understanding. More specifically:
>
>
>
> - Do we have a link to the draft specification in PDF or other format?
>
> - What is the next deadline? I think we have one on July 31th, do I
>
> remember right?
>
> - Can you confirm me that the license of final interfaces will be
>
> BSD-like?
>
>
>
> Thanks,
>
>
>
> Martin
>
>
>
>
>
>
>