I know I’m still shooting for Friday for mine. I was delayed a bit by the Eclipse outage over the weekend. I know my Connectors one is waiting for Tom’s transactions. Do we know if we have any key
api on the critical path at the moment?
Steve
From: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx <jakartaee-spec-project-leads-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 12 February 2020 14:24
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Subject: Re: [jakartaee-spec-project-leads] Making progress on the APIs, but need another push...
The goal for Friday (02/14/2020) was to have all of the API jar files available as Milestone or Release Candidate artifacts in Maven Central. The idea was to have all of the APIs available for other projects' usage -- compiling, building,
testing, etc. There was no planned Platform API build for Friday. Just a project goal. We may have a couple of trailers, but I would really like to see the majority of the updated APIs available in Maven by Friday.
FYI, the waves designation is more for the next step of actually prepping the component for the final releases. As components prep their final APIs, Specs, and TCKs, we need an ordered priority of which projects need to go first, second,
etc. This is where the waves come in. For the APIs, we're expecting all projects to have their APIs available in Maven with no regard to "waves".
Is the expectation that all waves will have an build on Friday? If so then transactions may not be ready as it stands. If the waves release in order we can then include dependency upgrades to milestone/RC's of other Jakarta projects our
projects use. For transactions that would be interceptor and CDI. If that is not the plan then we will need to plan further milestones with changes in once we consume updated dependencies.
Hi,
We have a checkpoint coming up next Friday, Feb 14, for the Milestone/Release Candidate API jar files being available in Maven Central.
Our wave:1 projects are making great progress on delivering those updated APIs:
https://github.com/orgs/eclipse-ee4j/projects/17?card_filter_query=label%3Awave%3A1
But, all of the other waves need some work... If your team is working on this and close to delivering, Great! But, if you know that your Specification Project team will *not* be able to meet this
deadline, please speak up, explain the hurdles, and ask for assistance. There are many participants through out this Jakarta EE community that might be able to step up and help out. You can reply to this note, or update your Epic Issue, or send Steve or
myself a private email, or find us on Slack (I am on
javaee-wg.slack.com). Thanks for your help!
---------------------------------------------------
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
_______________________________________________
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
|