Thanks, I now see the additional incubation guidelines. So we wil: 1. Remove the versions from pypi- immediately (will be taken care of tonight) 2. Add the incubator-specifics to our dev release and get @JB to review 3. Create a formal release following (2) - within the next week or so hopefully.
Thanks again for pointing this out. Assaf On Sat, Dec 19, 2020 at 12:48 AM Justin Mclean <[email protected]> wrote: > HI, > > > 1. We are allowed to create internal dev. releases (e.g. "nightly") > without > > following an official apache release. We put them in pypi so that > > community members can easily build a local working apache liminal env. > > Based on Justin's input, it seems that this was not acceptable, is that > the > > case? > > In short an artefact created that way is not a release. For it to be a > release is must be voted on by the PPMC/IPMC. A podling can't place > unreleased material that can be accessed by the general public and it > shouldn't give the public instructions on how the get that. [1] > > > We created these > > <https://github.com/apache/incubator-liminal/blob/master/dev/RELEASE.md> > > This is missing the release vote by the Incubator PMC. The PPMC (not PMC) > cannot approve releases, the Incubator PMC needs to do that. [2] While in > the Incubator you need to do things slightly differently as you are not a > opt level project yet. > > Thanks, > Justin > > 1. https://infra.apache.org/release-distribution.html#unreleased > 2. https://incubator.apache.org/policy/incubation.html#releases >
