Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [microprofile-wg] Review Initiation for MicroProfile GraphQL 1.0.4

Ok, I think I understand the process better now.  

It sounds like since MP GraphQL versions 1.0.0-1.0.3 were released prior to the MPWG, we cannot release a 1.0.4, period.  It must be 1.1 (minor) or 2.0 (major).

It sounds like our only course of action here is to "re-brand" 1.0.4 as 1.1.  I think this will result in some user confusion as there is no new, user-visible function in this minor release. I suppose the other alternative would be to wait to release anything until we have some user-visible function ironed out (like the client APIs), but this will obviously have impact to some vendors.

Thanks for the clarification,

Andy

On Tue, Mar 9, 2021 at 10:26 AM Emily Jiang <emijiang6@xxxxxxxxxxxxxx> wrote:
Hi Andy,

I think you referred to this discussion. On that thread, we focused on whether you can get an exception for not going through a ballot or defining a lightweight process for service release. On that thread, I commented that you need to do a release first using the EFSP process and you won't be able to get an exception nor a lightweight process. I think what Kevin suggests the release should be called a minor release even though sometimes it might be a service release from a functional point of view. After rereading the EF process (A Specification Team must have engaged in a successful Release Review for a Major or Minor Release prior to engaging in a Service Release.), I agree with Kevin that this release should be a minor release.

Hope this helps with clarifying the situation!

Thanks
Emily

On Tue, Mar 9, 2021 at 4:01 PM Andy McCright <j.andrew.mccright@xxxxxxxxx> wrote:
Hi Kevin,

The intent of this request is to release the 1.0.X stream under the EFSP.  You are right that the 1.0.0-1.0.3 releases were performed prior to the establishment of the MPWG. Our understanding of the process is that in order to make future service/micro releases, we would need to first release under the EFSP/MPWG process. I believe Emily said this on the MP Community mail list last month.  If we are not following the correct process, can you point us to the right process page?

Thanks,

Andy

On Tue, Mar 9, 2021 at 9:53 AM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
Hi Phillip,
Similar comments as the OpenAPI request...

A service release (1.0.4 in your case) can not be performed until a corresponding major or minor release has been performed under the Eclipse Foundation Specification Process:

From the EFSP (I have highlighted the requirement):

Service Releases
A Service Release includes only minor changes and/or clarifications over a Major or Minor Release. Specifically, a Service Release must not include any significant new features and/or breaking changes. A Specification Team may consult with their PMC and Specification Committee to determine precisely what constitutes a minor change and/or clarification.
A Specification Team must have engaged in a successful Release Review for a Major or Minor Release prior to engaging in a Service Release. No Progress Review is required for a Service Release; the Specification Team must, however, engage in a successful Release Review.

From what I can tell, the GraphQL 1.0 release was not performed under the EFSP.  And, from the description of the release ("Other changes include a fix in the TCK to allow any order of properties when describing a default value in the schema and a fix in the API to allow `@NonNull` on parameter"), this sounds like it goes beyond the definition of a service release.  So, maybe this should be a 1.1 release?


---------------------------------------------------
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:        Phillip Kruger <phillip.kruger@xxxxxxxxx>
To:        EMO@xxxxxxxxxxxxxxxxxxxxxx
Cc:        microprofile-wg@xxxxxxxxxxx
Date:        03/06/2021 05:57
Subject:        [EXTERNAL] [microprofile-wg] Review Initiation for MicroProfile GraphQL 1.0.4
Sent by:        "microprofile-wg" <microprofile-wg-bounces@xxxxxxxxxxx>



We have staged MicroProfile GraphQL 1.0.4 final release with the release planand created this issuelisting the various release artifacts. Please can you initiate the review process?


Thanks

Phillip on behalf of MicroProfile GraphQL_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/microprofile-wg


_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/microprofile-wg
_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/microprofile-wg


--
Thanks
Emily

_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/microprofile-wg

Back to the top