Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [External] : Re: [jakartaee-spec-project-leads] : Re: Next iteration of Jakarta EE 9.1 Release Plan

Hi Kevin,

> On Feb 18, 2021, at 4:38 PM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
> 
> Hi Lukas,
> Technically, you do not have an end of March deadline.  Since service releases are (will be) defined as having zero functional changes, we want the ability to deliver service releases at any time.

I agree, this makes sense


>  They would not be considered part of a "platform release".  The Jakarta EE 9.1 platform consists of the same major.minor releases of all Specifications are Jakarta EE 9.  We would not modify the content of Jakarta EE 9.1 Specification to explicitly designate service releases as being included.

The platform release will need at least one CI and it just makes sense to me for the CI to include latest service releases of included projects - be it specs or impls. In the other words it is about allignment with upcoming GF release. Ability to provide service releases between various GF - or generally arbitrary platform CI - releases is great to have but issuing one say a week after platform CI update goes out would look strange to me from end-users perspective (unless there is ie security fix or sth else of the same importance).

Thanks,
—lukas

> 
> On the other hand, if there are service release updates for the javadoc that could be picked up for the 9.1 Javadoc collection, that would be great.  The API pom files would need to be updated accordingly:
> https://github.com/eclipse-ee4j/jakartaee-api/blob/master/pom.xml



> 
> For your Jakarta Mail implementation question...  You are only governed by the Eclipse Development Process (not the Spec Process) for implementations.  You can go forward with your service releases for the Jakarta Mail implementation as you see fit.  And, you are correct, if you have already delivered a major or minor release of Jakarta Mail within the past year, then the release process is simplified.  Good luck!
> 
> ---------------------------------------------------
> Kevin Sutter 
> STSM, Jakarta EE and MicroProfile architect @ IBM
> e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)    
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
> 
> Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)
> 
> 
> 
> From:        Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>
> To:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
> Cc:        JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
> Date:        02/18/2021 09:22
> Subject:        Re: [jakartaee-platform-dev] [External] : Re: [jakartaee-spec-project-leads] Next iteration of Jakarta EE 9.1 Release Plan
> Sent by:        "jakartaee-platform-dev" <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
> 
> 
> 
> Hi Kevin,
> 
> > On Feb 18, 2021, at 2:34 PM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
> > 
> > Hi Lukas!
> > Trying not to ignore you!  It's just that I'm still working with the Spec Committee to ensure that the process can be simplified for a Service Release (x.y.z).  As the Specification Process is currently written, it can be interpretted that a Service Release needs to go through the full process.  Several of us on the Spec Committee do not agree with this interpretation and we're trying to figure out a compromise.  We're making progress, but I can't give a definitive answer yet.
> 
> 
> Those 2-3 weeks required for ballot itself are what is starting to worry me given there are already less than 6 weeks left till the end of March - if the current intent is to not miss that target then there is not much time...
> 
> Btw: I have also Mail 1.6.6 in the queue (not something for 9.1) - it’s a service/bug fix release (no API, javadoc change, just bug fixes in implementation). Since mail as such is API/spec+Impl project what rules do apply here?  Those for spec project (ie including ballot) or those for implementation project (since this is within a year of the last release, I can just go ahead and publish it)?
> 
> > 
> > If you want to make immediate progress with your proposed service releases, you could start down the path of producing the PRs, Release Records, etc of a normal release cycle.  That process will work just fine.  But, as we all know, there is overhead associated with that process and, thus, we're trying to simplify it for everyone.
> 
> I’m not blocked, I’m still moving on by employing staging repo ;-)
> 
> Thanks,
> —lukas
> 
> > 
> > Thanks for the note. 
> > 
> > ---------------------------------------------------
> > Kevin Sutter 
> > STSM, Jakarta EE and MicroProfile architect @ IBM
> > e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
> > phone: tl-553-3620 (office), 507-253-3620 (office)    
> > LinkedIn: https://www.linkedin.com/in/kevinwsutter
> > 
> > Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)
> > 
> > 
> > 
> > From:        Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>
> > To:        JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
> > Cc:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
> > Date:        02/16/2021 13:27
> > Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Next iteration of Jakarta EE 9.1 Release Plan
> > Sent by:        "jakartaee-platform-dev" <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
> > 
> > 
> > 
> > Hi Kevin,
> > 
> >   Any update on how to proceed with service releases of the spec projects? Is release review and ballot required or can some or all these steps be skipped and I can just go ahead with publishing artifacts whenever they are ready?
> > 
> > Thanks,
> > —lukas
> > 
> > > On Jan 7, 2021, at 6:50 PM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
> > > 
> > > Hi,
> > > First of all, thank you for the discussions on the original "gather ideas" documentand the Platform calls regarding the scope and content of Jakarta EE 9.1.  Based on this input, I have attempted to create a more concise Jakarta EE 9.1 Release Plan:  https://docs.google.com/document/d/1fEf-Iio2-NJSfMuNc1rpCxIMdA6tlUyv8d2c4TydMt0/edit?usp=sharing
> > > 
> > > I would appreciate some additional reviewing and commenting so that we could present this Release Plan to the Specification Committee in the next couple of weeks.  We will plan to discuss this at our Platform call this coming Tuesday at 10am Central:  https://calendar.google.com/calendar/u/0/embed?src=eclipse-foundation.org_1hv9g07snptd5gnkbgkvef5d3s@xxxxxxxxxxxxxxxxxxxxxxxxx
> > > 
> > > Some of the highlights of this EE 9.1 Plan...
> > >                  • Limit the release to support the Java SE 11 runtime.
> > >                  • No API updates to the component Specifications.
> > >                  • Platform Specifications will need to be updated to define the support beyond Java SE 8.  And, the TCKs and Compatible Implementations will most likely need to be updated to allow support of Java SE 11.
> > >                  • And, that's about it...
> > > 
> > > The goal is to produce this release in 1Q2021, thus the limitations on what might be included.  Originally, Jakarta EE 9 was going to support both Java SE 8 and 11.  The support for Java SE 11 would have caused us to miss our deliverable date for EE 9, so it was pushed out to Jakarta EE 9.1.  Let's just finish that job and do the minimal amount of effort to support Java SE 11 with Jakarta EE 9.1.
> > > 
> > > Comments are welcome using this mail thread, or the Release Plan document, or the Platform call.  Thanks!
> > > 
> > > ---------------------------------------------------
> > > Kevin Sutter 
> > > STSM, Jakarta EE and MicroProfile architect @ IBM
> > > e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
> > > phone: tl-553-3620 (office), 507-253-3620 (office)    
> > > LinkedIn: https://www.linkedin.com/in/kevinwsutter
> > > 
> > > Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)
> > > _______________________________________________
> > > 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-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://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads__;!!GqivPVa7Brio!O75h29RbjaMgKhphZkA4mtGQ8SW1PGGn1QReQiac1vKWMkODIBsNhVjmaeiTl2-HZEI$ 


Back to the top