[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakarta.ee-spec.committee] Last steps in Spec. approval?
|
The index page has been updated. So far as I can tell it looks
complete and I have replaced 'draft' tag with the 'complete' tag.
Kevin if there is another mark, please correct and/or apply it.
Great job Scott and the (C)DI committer team!
On 8/3/2020 3:52 PM, Ed Bratt wrote:
OK. I have requested the links be updated. Other than that I
think DI is ready to go. I don't know if anyone else wants to
have a look....
On 8/3/2020 3:23 PM, Kevin Sutter
wrote:
Ed,
The PRs are
not merged until the ballots are completed. At this point, if
you are happy with the PRs and feel they are ready for ballot,
then you should mark the PRs are "Approved" (from a Review
standpoint). That should be the indication that a Spec
Committee member has done due diligence on reviewing the PRs
and they are now ready for ballot.
Once the
ballots are initiated, then the vote is open for two weeks.
Once the ballot is approved, then we have another checklist
to perform post ballot, which can be found here: https://github.com/jakartaee/specification-committee/blob/master/spec_finalization_checklist.md
All of the
items in the _index.md files should be in their expected final
form/location. The keys should not change just because they
are promoted (that's what we determined for Jakarta EE 8).
Hope this
helps!
BTW,
most/all of this is documented in our Operations Guide: https://jakarta.ee/committees/specification/operations/
If this
needs some updates and clarifications, please submit PRs to
make the instructions better. Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx
Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Ed
Bratt <ed.bratt@xxxxxxxxxx>
To:
Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
08/03/2020
16:58
Subject:
[EXTERNAL]
[jakarta.ee-spec.committee] Last steps in Spec. approval?
Sent by:
jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
I believe the Dependency Injection
Spec. is ready to go (PR 221). (it's probably been ready to go for
several days now, but I've been looking at other things :-( ).
The TCK needs to be moved to the final download location and
the SHA and PUB key files need to be created.
How are these created?
As the mentor, do something to
create these? Do I click the "Merge" button on the PR? Who
updates those final three links (TCK d/l, SHA255 file, and
Pub. Key file)? I can predict the links, so I conceivably
could just request the changes -- then, who pushes the button
to promote the TCK and generate the actual files?
the state location for the TCK is:
https://download.eclipse.org/ee4j/cdi/inject/2.0/jakarta.inject-tck-2.0.1-bin.zip
From that, I think the finals are:
Thanks,
-- Ed_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee