Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rest-dev] [External] : Re: M1 action items
Hi,

On Tue, 5 Dec 2023 at 16:13, Santiago Pericasgeertsen via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

 What’s the expectation for the release review of 1/30 then? 

For the release review of 30/1/2024 the spec should be done, so formal release reviews can start. 


Kind regards,
Arjan Tijms

 

— Santiago


There will most likely be a request for a M2 in January or February.

Ivar

On Tue, Dec 5, 2023 at 9:45 AM Santiago Pericasgeertsen <santiago.pericasgeertsen@xxxxxxxxxx> wrote:
Ivar,

 I think it’s good for the platform team to provide some guidance and for the specs to comply with them. Having said that, if M1 is targeted for the end January, asking components to push artifacts nearly two months before seems unnecessary; it would make a lot more sense for the deadline to be two weeks before or something similar to that. IMO, it should be more important to deliver useful artifacts that people can use (it will certainly not be the case for Jakarta REST M1) than to meet some random dates. 

 My 2 cents.

— Santiago

On Dec 5, 2023, at 9:25 AM, Ivar Grimstad via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

Hi Markus,

Yes, it is true that it is ultimately your decision. However, the Platform Team's request is that Maven Central be used as this release's purpose is to make the API artifacts available for all implementers to consume. All the other specifications targeting Jakarta EE 11 have complied with this.

Ivar

On Tue, Dec 5, 2023 at 9:19 AM Markus Karg <markus@xxxxxxxxxxxxxxx> wrote:

(1) Nothing says that Maven Central MUST be used for publication. There are lots of other repos we could use to fulfil that email. (2) It might be the case that the Platform team likes this to happen, but still this is the Jakarta REST committer's decision if and what they put on Maven Central.

-Markus

 

 

Von: Ivar Grimstad [mailto:ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx] 
Gesendet: Dienstag, 5. Dezember 2023 13:38
An: Markus Karg
Cc: Jakarta Rest project developer discussions
Betreff: Re: [rest-dev] M1 action items

 

Here is the request from the Jakarta EE Platform Project:

 

 

In short:

 

This message is your notice that the EE 11 platform project expects you, as a component spec project, to produce your first milestone release for EE11 by 23:59 EST on 2023-11-28. 

 

Requirements

 

We want to keep the bar low for EE 11 M1. We realize we are all trying to get our milestone release producing engines started. M1 does not require a TCK or an implementation, though it would be better if you had those. We will require those for M2. Here's what you need to hit M1.

  • API jar released to maven central
    • groupId: same as EE 10
    • artifactId: Same as EE 10
    • version: whatever your version number is for EE11 followed by "M1" For example for Jakarta Faces it would be 5.0.0-M1.
  • Spec document
  • Javadocs
  • XML schemas (if the spec has XML schemas)

 

 

 

On Tue, Dec 5, 2023 at 7:20 AM Markus Karg <markus@xxxxxxxxxxxxxxx> wrote:

When did the Jakarta REST committers decide to do that?

-Markus

 

 

Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Ivar Grimstad via rest-dev
Gesendet: Dienstag, 5. Dezember 2023 11:09
An: Jakarta Rest project developer discussions
Cc: Ivar Grimstad
Betreff: Re: [rest-dev] M1 action items

 

Yes, the Milestones should be published to Maven Central.

 

Ivar

 

On Tue, Dec 5, 2023, 02:32 Markus Karg via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

Maybe I missed something, but why should we publish milestones publicly? IMHO we never did so befere.

If there is a concensus to publish milestones I will be happy to press that button for you.

-Markus

 

 

Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Jim Krueger via rest-dev
Gesendet: Dienstag, 5. Dezember 2023 03:13
An: rest Jakarta project developer discussions
Cc: Jim Krueger
Betreff: [rest-dev] M1 action items

 

Hi,

After some tweeking I was able to get the Jenkins job to put the jakarta.ws.rs-api-4.0.0-M1 artifacts to staging (https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/ws/rs/jakarta.ws.rs-api/4.0.0-M1/).

 

Please take a look at these to ensure they are correct.   Assuming they are, if somebody on this list has authority and knowledge to run the Jenkins job to publish these to Maven Central please do so.

 

Beyond this, to finish M1 we will also need the following actions done:

 

  • Build the specification from the Release-4.0 branch 
  • Add links to the M1 APIs in maven central and the M1 Specification to the project site

 

Thanks

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org


 

-- 

Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 


-- 
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://accounts.eclipse.org__;!!ACWV5N9M2RV99hQ!KjjfVvl16TIEWDq9g9KO_zLMDwDsHe_w0p1EI673XM8RZZfnPIpFM4b1KNanWikFnxEgyMHv4B-rkjiomAcLc9Q3MMeG$ 



-- 
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

Back to the top