Incubating PMC rejecting releases should not be a problem for the version numbering as we will bring forward RCs so we could have RC1 RC2 RC3 RC4 on the same version until the last RC is voted and released that’s why the “RC1” string should not be part of the file/archive and is part of the parent folder/directory
So an example we could have dev/0.1.0-RC1/openwhisk-0.1.0.tgz dev/0.1.0-RC2/openwhisk-0.1.0.tgz dev/0.1.0-RC3/openwhisk-0.1.0.tgz Once the last RC approved and voted by IPM PMC archive gets move to dist dist/incubator/openwhisk/0.1.0/openwhisk-0.1.0.tgz - Carlos Santana @csantanapr > On Mar 15, 2018, at 8:55 AM, Bertrand Delacretaz <[email protected]> > wrote: > >> On Thu, Mar 15, 2018 at 1:28 PM, Carlos Santana <[email protected]> wrote: >> ...Not sure what are the Apache policy if any about 0.x and 1.x ... > > There's no ASF policy for that, but a common perception than a 1.x > release is "reasonably finished", whatever that means. > > Note also that's it's common for the first few release candidates of a > podling to be rejected by the Incubator PMC who has the final say on > them (for formal reasons, missing disclaimers etc, unrelated to code > quality), so it might be useful to avoid "wasting" nice release > numbers during that phase. > > -Bertrand
