Re: [jakarta.ee-spec.committee] Release records for projects with multip

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

The release record serves as a means of communicating release plans to the community. As such, it should be created as early in the development cycle as possible. It also serves as the anchor  for reviews and EMO processes around reviews and must be created before we start the ballot.

Release records are for projects. As such, a single release record is sufficient for a single project that is releasing multiple specifications at the same time. The description field in the release record should be used to describe the nature of the release (e.g., list the specification releases included).

Wayne

On Sat, Jul 18, 2020 at 12:52 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Hi,

In the Specification committee Operations Guide, under the section "Creating a Final Specification," step 8 indicates that a formal release record must be created.

I'm currently reviewing Dependency Injection (wave 1) which is included in the Context and Dependency Injection project. Presumably, a release record won't be created until the CDI spec (wave 3) is readied for release.

I presume this is okay, but could someone confirm?

This implies that all the formal EMO and PMC work won't be done, before this specification has completed its ballot. Assuming this is accptable, will these notifications (for CDI) need to include references for both DI and CDI? (I think a consequence of this is that all the EMO and PMC validation work will be done after the DI ballot has been completed. I don't know if that is acceptable, or not.)

Thanks,

-- Ed

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020 - October 20-22