| Re: [jakarta.ee-spec.committee] Release records for projects with multiple specifications |
There are similar references, listed as ballot prerequisites in the Specification Committee, spec_finalization_checklist.md as well.
Alternatively, a release record for DI could be necessary but I
don't know how the tools would support a release of DI only so I
don't know how we'd advise the DI project team to take the proper
steps. It certainly appears as if the tooling is intended to
support a single relationship between a project and a release,
though I'm happy to be shown this is incorrect.
-- Ed
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