Hi Justin Thanks for the clarification.
The release of shardingsphere 3.0.0M1 and 3.0.0 were just before the shardingsphere code move to Apache. There are some discussion about it in the Infra JIRA[1]. It may be a gray area for the project to the release outside of apache after the incubation vote and before the code transfer. As these releases are not Apache approved releases, my suggestion is we should mention it in the website and github release page. [1]https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17289 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Jan 30, 2019 at 12:35 PM Justin Mclean <[email protected]> wrote: > > Hi, > > I’d allso ask the advice of your mentors and see what they suggest. > > Here’s the relevant ASF policy: > "If the general public is being instructed to download a package, then that > package has been released. Each (P)PMC must obey the ASF requirements on > approving any release” [1] > "at least three (P)PMC members must vote affirmatively for release,” [2] > "In order for a podling to receive full permission from the IPMC to execute > the release, the release vote must be held on the incubator general list” [3] > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html#what > 2. http://www.apache.org/legal/release-policy.html#approving-a-release > 3. > https://incubator.apache.org/guides/releasemanagement.html#podling_constraints
