| Re: [rest-dev] [External] : Re: Please release an artifact for inclusion in EE 11 Milestone 1 |
We have to plan according to the facts, not trying to fake facts just to follow a plan. I do not see any benefit from pushing a 4.0.0-M1 to Maven Central that essentially does not contain at least the essential backwards-incompatible changes planned (i. e. CDI). IMHO the correct resolution would be: * Jakarta EE 11 will contain the latest feature release actually existing on Maven Central on March 1st, even if that might only be JAX-RS 3.1 still. It makes no sense to enforce that this has to be the exact number 4.0.0 as this would just hold the train OR produce empty fake releases. * JAX-RS 4.0 will be published when it's done, not earlier. We do not publish empty fake releases. Not even when asked for by our good friends Ed, Arjan and Ivar. ;-) * I do not see any need to agree to ANY deadline (not even to one that we would give us ourselfs), as apparently nobody is able to commit to ANY deadline. * We should separately discuss if we need more manpower and how to get those additionals hands. Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Santiago Pericasgeertsen via rest-dev Jim, We should discuss the current schedule for EE 11 and the work left to deliver Jakarta REST 4.0. As I stated in other messages, I’m skeptical we have the manpower to deliver a high-quality release given the current timeframe. My suggestion would be to resolve this first before pushing any artifacts to Maven central. — Santiago On Dec 18, 2023, at 9:35 AM, Jim Krueger via rest-dev <rest-dev@xxxxxxxxxxx> wrote: Thanks Ed. Jakarta Rest Committers, Does there remain any objections to moving the M1 version at https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/ws/rs/jakarta.ws.rs-api/4.0.0-M1/ to maven central? This is most certainly a preliminary version that is going to be subject to multiple changes in the upcoming months. Please respond if anyone stills feel that this should not be applied to maven central. Thanks On Dec 18, 2023, at 8:14 AM, Ed Burns via rest-dev <rest-dev@xxxxxxxxxxx> wrote: Executive Summary Please push out a release to maven central of your API, sources, and javadoc jars with the version number major.minor.micro-M1 where major.minor.micro is ideally what you intend to include in EE 11, but really can be any number you want that is semVer greater than your current release. Every other component spec in EE 11 has already done this. We are holding the entire EE 11 M1 release waiting for jax-rs. Details Please excuse the fact that my first email to your community in my role as EE 11 co-release coordinator is so intrusive and demanding. As you know, Arjan and I are trying to do something that hasn't been done before during Jakarta EE release cycles: produce milestone releases on the way to the final release. The decision to produce milestone releases in this way was recorded in the 2023-09-19 platform project meeting minutes. The latest details about this plan are described in this email I sent to spec-project-leads on Wednesday 2023-12-13. This email links to the latest release plan. In this plan, REST is in Wave 5.
Any spec, including jax-rs, is free to produce as many releases as they want, whenever they want, and we'll just pick up the latest available one at the time we need to do a milestone release. We leave the door open to do further milestone releases, but we expect that M4 will function as a release candidate. Thanks, Ed and Arjan | edburns@xxxxxxxxxxxxx | office: +1 954 727 1095 | Calendar Booking: https://aka.ms/meetedburns | | Please don't feel obliged to read or reply to this e-mail outside | of your normal working hours. | | Reply anonymously to this email: https://purl.oclc.org/NET/edburns/contact _______________________________________________ _______________________________________________ |