> The
specification project team should go through the merged spec website page
to verify all the links are valid.
> Please can you let me know,
is this website available to be reviewed? I don't think the /specifications
repo is using github pages so I presume some process builds this repo and
publishes it some place?
It looks like
this website is now live and being updated! https://jakarta.ee/specifications/
Great! I will check it again tomorrow as transactions is not uploaded yet but good to see the site is broadly available!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Tom
Jenkinson <tom.jenkinson@xxxxxxxxxx>
To:
JakartaEE
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Date:
09/04/2019
07:30 AM
Subject:
[EXTERNAL]
Re: [jakartaee-spec-project-leads] Required actions after spec is
approved
Sent
by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
On Tue, 3 Sep 2019 at 20:59, Bill Shannon
<bill.shannon@xxxxxxxxxx>
wrote:
After a specifications is approved, a
Specification Committee member will add this checklist to the Pull Request
for the specification:
- On ballot completion
- The designated specification committee
representative adds this final checklist to the main PR.
- The specification committee representative
merges the specification PRs.
- The designated specification committee
representative calculates the staged EFTL TCK signature and promotes it
to the committee download area using the https://ci.eclipse.org/jakartaee-spec-committee/job/promote-release/job.
- The specification project member who
created the staging release promotes the specification api jars to maven
central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
- The EMO updates the specification page
with the ballot results. This list goes on the committed spec index page.
- The specification project team should
go through the merged spec website page to verify all the links are valid.
Please can you let me know, is this website
available to be reviewed? I don't think the /specifications repo is using
github pages so I presume some process builds this repo and publishes it
some place?
- The specification project team should
approve the compatibility request.
- The compatible implementation project/vendor
MUST send an email tck@xxxxxxxxxxxfor approval of the compatible implementation for trademark usage.
- The specification project team should
merge any final release branch as appropriate for the branch management
for the project.
Note that several of the items must be
done by members of the specification project team. That means you!
Whoever submitted the Pull Request should
be notified when the checklist is added. At that point you need to
make sure the project team activities are completed and checked off in
the checklist.
Let me know if you have any questions.
Thanks.
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads