| Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Action Required for Jakarta EE 9 Milestone Release |
If GlassFish are in the middle of a build, perhaps they already pulled the old jar. I sent a message to them, will give them just a little bit longer to respond.On Thu, 11 Jun 2020 at 17:21, Scott Stark <starksm64@xxxxxxxxx> wrote:It won't because the staging profile sees that virtual repository view, and it will be updated to the new build as soon as the old staging repository id is dropped. The order should be to build the new release, then drop the previous staged repo id so that there is no point at which the RC2 is not available._______________________________________________On Thu, Jun 11, 2020 at 11:06 AM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:I wonder if it would matter to the Glassfish team if the build of glassfish used a version of a Jar that was dropped? I will ask the glassfish community too (added to this thread). I would hope because the Java code should be the same it wouldn't be a major problem for them.OK, so unless I hear otherwise I will drop the RC2 in staging, produce and release a new RC2 which has the Javadocs licence update._______________________________________________On Thu, 11 Jun 2020 at 16:59, Scott Stark <starksm64@xxxxxxxxx> wrote:_______________________________________________I would just rerun the release job to update the RC2 staging contents and then release that to maven central. You would need to drop the previous repository so that the virtual repository:is updated with the current staged content.On Thu, Jun 11, 2020 at 10:03 AM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:I need a little bit of guidance.I was holding off on pushing Jakarta Transactions RC2 out of staging. We now have an update to the Javadocs that has a useful clarification to the licensing merged into master. I could therefore re-issue an RC2 with it in. There should be no code changes to the API.However, that will push a new version of the jar and I am now thinking that is not a good idea as Glassfish should have been built with the version from staging.This is important as I plan to produce the PR for: https://github.com/jakartaee/specificationsWhat I am thinking is to release the RC2 jar from staging, then to do use the Javadocs from master.Does anyone see a problem with that?_______________________________________________On Wed, 10 Jun 2020 at 19:29, Kevin Sutter <sutter@xxxxxxxxxx> wrote:Hi Tom,
I'm going to indicate that it is Strongly Recommended to release the API artifacts to Maven Central, but it is not a firm Requirement. Not for the Milestone. As Lukas pointed out, there are more customers than just the Platform and Web Profile APIs which may be interested in the individual Component APIs. So, please consider it. 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: Tom Jenkinson <tom.jenkinson@xxxxxxxxxx>
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Cc: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 06/10/2020 12:09
Subject: [EXTERNAL] Re: [jakartaee-spec-project-leads] [jakartaee-platform-dev] Action Required for Jakarta EE 9 Milestone Release
Sent by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
If it is required for API artifacts to be further on than staged, please do let me know.
On Wed, 10 Jun 2020 at 18:04, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:I think the idea is that the RCx and Mx jars will be released to maven central for the June Jakarta EE 9 overall milestone release?
-----Original Message-----
From: jakartaee-platform-dev-bounces@xxxxxxxxxxx<jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Lukas Jungmann
Sent: 10 June 2020 18:00
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>; Tom Jenkinson <tom.jenkinson@xxxxxxxxxx>
Cc: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Action Required for Jakarta EE 9 Milestone Release
On 6/10/20 6:45 PM, Tom Jenkinson wrote:
> Is it enough for the RC to be in staging or does it need to be
> released fully?
by keeping it in staging only you are blocking your potential consumers in providing their projects to public for testing and for early adoption through maven central.
Keep in mind that GlassFish is not the only consumer of these artifacts.
thanks,
--lukas
>
> Thanks,
> Tom
>
> On Wed, 3 Jun 2020 at 00:34, Kevin Sutter <sutter@xxxxxxxxxx
> <mailto:sutter@xxxxxxxxxx>> wrote:
>
> Sorry, forgot to mention...
>
> The specific action I am requesting is for each Spec Project to
> create the PRs to update your project's_index.md file in the
> Specifications repository
> (https://github.com/jakartaee/specifications). Whatever artifacts
> you have available for this Milestone, you are welcome to publish --
> the Specs, the APIs, the TCK, or the CI. The template when creating
> the PR will help with filling in the blanks.
>
> But, you can also just reference existing files and/or PRs for examples:
>
> CDI 3.0 _index.md file:
> https://github.com/jakartaee/specifications/blob/master/cdi/3.0/_index.md
> CDI 3.0 PR: https://github.com/jakartaee/specifications/pull/157
>
> Please raise questions if this is not clear. Thanks!
>
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect @ IBM
> e-mail: sutter@xxxxxxxxxx<mailto:sutter@xxxxxxxxxx> Twitter:
> @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
>
>
>
> From: Kevin Sutter/Rochester/IBM
> To: "jakartaee-platform developer discussions"
> <jakartaee-platform-dev@xxxxxxxxxxx
> <mailto:jakartaee-platform-dev@xxxxxxxxxxx>>, "JakartaEE Spec
> Project Leadership discussions"
> <jakartaee-spec-project-leads@xxxxxxxxxxx
> <mailto:jakartaee-spec-project-leads@xxxxxxxxxxx>>
> Date: 06/02/2020 18:26
> Subject: Action Required for Jakarta EE 9 Milestone Release
>
> ----------------------------------------------------------------------
> --
>
>
>
> Hi,
> With the Jakarta EE 9 Milestone Development deadline coming up very
> fast (*June 12*), we need to get your Project Specification Page PRs
> in place. About a third of the Projects have already submitted the
> PRs, but we still need about 20 more Projects.
>
> Milestone progress for submitted PRs:
> _https://github.com/jakartaee/specifications/milestone/4_
> Remaining Projects (you need to be in the Milestone column):
> _https://github.com/orgs/eclipse-ee4j/projects/17#column-9442495_
>
> This is for your Project's benefit to publicly show the progress for
> each of your individual Projects -- the current state of your Specs,
> APIs, TCKs, and CIs. Of course, we will be publicizing the overall
> progress at the Platform (and Web Profile) level, but it would also
> be good to publicize your individual progress. Thanks for your help!
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect @ IBM
> e-mail: sutter@xxxxxxxxxx<mailto:sutter@xxxxxxxxxx> Twitter:
> @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: _https://www.linkedin.com/in/kevinwsutter_
> ----- Forwarded by Kevin Sutter/Rochester/IBM on 06/02/2020 18:18
> -----
>
> From: Kevin Sutter/Rochester/IBM
> To: jakartaee-platform developer discussions
> <jakartaee-platform-dev@xxxxxxxxxxx
> <mailto:jakartaee-platform-dev@xxxxxxxxxxx>>
> Cc: "JakartaEE Spec Project Leadership discussions"
> <jakartaee-spec-project-leads@xxxxxxxxxxx
> <mailto:jakartaee-spec-project-leads@xxxxxxxxxxx>>
> Date: 05/28/2020 09:43
> Subject: Re: [EXTERNAL] [jakartaee-platform-dev] Milestone Release
> Planned for June
>
> ----------------------------------------------------------------------
> --
>
>
> Hi,
> Making a little bit of progress... Andy McCright just submitted the
> PRs for the Restful WebServices Milestone! They are looking good
> and should be merged shortly... I'm using the Jakarta EE 9
> Milestone 1 github milestone for tracking our progress..._
> __https://github.com/jakartaee/specifications/milestone/4_
>
> Sure would be nice to get more PRs available for reviewing and
> merging... Just throwing out an idea... Would it help to have an
> Issue on your backlog as a reminder of these required PRs? I know
> it's kind of covered by the Epic Issue for Jakarta EE 9, but since
> this Milestone release is in addition to the standard release
> process, just wondering if a reminder Issue would help. Let me
> know. Thanks!
>
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect @ IBM
> e-mail: sutter@xxxxxxxxxx<mailto:sutter@xxxxxxxxxx> Twitter:
> @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: _https://www.linkedin.com/in/kevinwsutter_
>
>
>
> From: "Kevin Sutter" <sutter@xxxxxxxxxx<mailto:sutter@xxxxxxxxxx>>
> To: "jakartaee-platform developer discussions"
> <jakartaee-platform-dev@xxxxxxxxxxx
> <mailto:jakartaee-platform-dev@xxxxxxxxxxx>>, "JakartaEE Spec
> Project Leadership discussions"
> <jakartaee-spec-project-leads@xxxxxxxxxxx
> <mailto:jakartaee-spec-project-leads@xxxxxxxxxxx>>
> Date: 05/26/2020 08:45
> Subject: [EXTERNAL] [jakartaee-platform-dev] Milestone Release
> Planned for June
> Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
> <mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx>
>
> ----------------------------------------------------------------------
> --
>
>
>
> Hi,
> Based on input from the _mailing list_
> <https://www.eclipse.org/lists/jakartaee-platform-dev/msg01721.html>and_last
> week's Platform call_
> <https://eclipse-ee4j.github.io/jakartaee-platform/minutes/2020-05-19.html>,
> we're pushing forward with a Jakarta EE 9 Milestone release in June.
>
> Since most of the Specification Projects have already delivered some
> type of Compatible Impl (CI) for the Glassfish effort, hopefully
> this request is just formalizing that effort and making the
> deliverables more accessible to our community.
>
> To that end, we are asking for all Specification Projects to update
> their _Specifications page_ <https://jakarta.ee/specifications/>with
> pointers to their most recent Specifications, APIs, TCKs, and CIs.
> This is easily done by creating a PR against the _jakartaee
> specifications repo_ <https://github.com/jakartaee/specifications>.
> Example from Dependency Injection:
> _https://github.com/jakartaee/specifications/pull/150_
>
> We need all of these PRs created, reviewed, and merged *before June
> 12*. As I mentioned, most of you should already have this material
> ready. We just need to formalize the delivery to make it more
> accessible. Please raise any questions or concerns with this process
> asap so that we have time to react. Thanks!
>
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect @ IBM
> e-mail: sutter@xxxxxxxxxx<mailto:sutter@xxxxxxxxxx> Twitter:
> @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn:
> _https://www.linkedin.com/in/kevinwsutter________________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> <mailto:jakartaee-platform-dev@xxxxxxxxxxx>
> To unsubscribe from this list, visit
> _https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev_
>
>
>
>
>
> _______________________________________________
> jakartaee-spec-project-leads mailing list
> jakartaee-spec-project-leads@xxxxxxxxxxx
> <mailto:jakartaee-spec-project-leads@xxxxxxxxxxx>
> To 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 unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
>
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To 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 unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To 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 unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev