Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Jakarta Bean Validation release approval 
On 9/21/20 6:46 PM, Scott Stark wrote:

The current process for finalizing a spec and artifacts after ballot:
https://github.com/jakartaee/specification-committee/blob/master/spec_finalization_checklist.md <https://urldefense.com/v3/__https://github.com/jakartaee/specification-committee/blob/master/spec_finalization_checklist.md__;!!GqivPVa7Brio!JJqKb6W9wTL4v6w3l65cPOVm4ShsmeCiiu7Vd6FBleJS2e79K03eSF1T9aU_9PJEB9Q$>
describes steps for a release review as something that happens during the run up to ballot.
I can see that https://github.com/jakartaee/specification-committee/issues/39 has not been touched yet
The interaction with the PMC and EMO have been described as asynchronous by Wayne Beaton in the past. If those are requirements for ballot completion, that needs to be made part of the process. 


Correct me if I'm wrong but as I understand it:
Ballot - an approval from the Jakarta EE WG for the release/a process defined by the spec committee Release review - an approval from Eclipse Foundation for the release/a process defined by Eclipse Foundation
* both can run in parallel; EF/EMO will wait for ballot to conclude and approve the release if and only if ballot passes 
* each checks different things (ie IP log, vendors' expectations,...)
* one needs to get both approvals in order to publish the release
What was the example of a project that had to re-release due to failed procedure?
not re-release, new minor release had to be done; projects affected by these requirements in the past were eclipselink, jsonp/b (one of them, don't remember which one exactly). 

thanks,
--lukas
On Mon, Sep 21, 2020 at 6:11 AM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx <mailto:lukas.jungmann@xxxxxxxxxx>> wrote: 

    On 9/16/20 4:43 PM, Scott Stark wrote:
     > Apparently we forgot to ask for approval of the Jakarta Bean
    Validation
     > 3.0 release. The ballot completed successfully and still needs
    approval
     > from the PMC.

    Probably a nit-pick but in the past it has not been possible to ask for
    the release approval post-mortem (when the bits has been already
    published) and new release had to be created to show that release
    followed all rules. From what I can see, approvals are to be done on
    Oct
    7th[1] but binaries are in central already[2]. Did something change? Is
    there any exception to the process[3] I'm not aware of?

    thanks,
    --lukas

    [1]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=566650
    <https://urldefense.com/v3/__https://bugs.eclipse.org/bugs/show_bug.cgi?id=566650__;!!GqivPVa7Brio!JJqKb6W9wTL4v6w3l65cPOVm4ShsmeCiiu7Vd6FBleJS2e79K03eSF1T9aU_riaJlf4$>
    [2]:
    https://search.maven.org/artifact/jakarta.validation/jakarta.validation-api/3.0.0/jar
    <https://urldefense.com/v3/__https://search.maven.org/artifact/jakarta.validation/jakarta.validation-api/3.0.0/jar__;!!GqivPVa7Brio!JJqKb6W9wTL4v6w3l65cPOVm4ShsmeCiiu7Vd6FBleJS2e79K03eSF1T9aU_JriYXwY$>
    [3]:
    https://www.eclipse.org/projects/handbook/#specification-project-reviews
    <https://urldefense.com/v3/__https://www.eclipse.org/projects/handbook/*specification-project-reviews__;Iw!!GqivPVa7Brio!JJqKb6W9wTL4v6w3l65cPOVm4ShsmeCiiu7Vd6FBleJS2e79K03eSF1T9aU_Ng3xM1w$>


     >
     >
    https://projects.eclipse.org/projects/ee4j.bean-validation/releases/3.0
    <https://urldefense.com/v3/__https://projects.eclipse.org/projects/ee4j.bean-validation/releases/3.0__;!!GqivPVa7Brio!JJqKb6W9wTL4v6w3l65cPOVm4ShsmeCiiu7Vd6FBleJS2e79K03eSF1T9aU_txKOMIA$>

     >
    <https://urldefense.com/v3/__https://projects.eclipse.org/projects/ee4j.bean-validation/releases/3.0__;!!GqivPVa7Brio!M1a-FyMIUbkDwiSDTLptkgJ-6i84NCsUNw81OsWLYC34MoL-9jtd8wX8cKyhTBaTNts$>
     >
     > _______________________________________________
     > ee4j-pmc mailing list
     > ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
     > To unsubscribe from this list, visit
    https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/ee4j-pmc__;!!GqivPVa7Brio!M1a-FyMIUbkDwiSDTLptkgJ-6i84NCsUNw81OsWLYC34MoL-9jtd8wX8cKyhk9CKTug$
     >
    _______________________________________________
    ee4j-pmc mailing list
    ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
    To unsubscribe from this list, visit
    https://www.eclipse.org/mailman/listinfo/ee4j-pmc
    <https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/ee4j-pmc__;!!GqivPVa7Brio!JJqKb6W9wTL4v6w3l65cPOVm4ShsmeCiiu7Vd6FBleJS2e79K03eSF1T9aU_icyfNPA$>


_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/ee4j-pmc__;!!GqivPVa7Brio!JJqKb6W9wTL4v6w3l65cPOVm4ShsmeCiiu7Vd6FBleJS2e79K03eSF1T9aU_icyfNPA$

Back to the top