The subject is a bit odd, but isn't https://github.com/apache an official Apache Software Foundation repository?
And https://github.com/apache/incubator-joshua/releases with the big blue Releases button seems suggestive (or confusing) to downstream users. The solution, due to GitHub's quirk, is to put tags after the vote. Doesn't seem that much of a trouble. --emi On Tue, Nov 29, 2016 at 10:02 PM, Tom Barber <t...@spicule.co.uk> wrote: > Personally I think thats over doing it a bit on the T&C's, the PPMC hasn't > created the artifact, I could create a release of any project and slap it > on github and people could download it, doesn't make it "official" though, > its just those faux-releases are generated by github themselves not a user. > > On Tue, Nov 29, 2016 at 7:55 PM, Justin Mclean <jus...@classsoftware.com> > wrote: > > > Hi, > > > > > IMHO, the tags on github are not formal releases. > > > > The tags may not be but it does creates a release artefact that someone > > can download. > > > > > So its not a violation of ASF release process. > > > > How so? It’s creating an artefact that the general public can access and > > download before the vote is over. [1] [2] seems quite clear on this. > > > > > Some projects have handled this by moving release votes to a different > > > (mirror/fork) of the project. > > > > You can just make the release on a branch rather than in a fork/mirror. > > > > Anyway I'll raise it on legal discuss. > > > > Thanks, > > Justin > > > > 1. https://www.apache.org/dev/release-distribution.html#unreleased > > 2. http://www.apache.org/dev/release.html#what > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > -- > Tom Barber > CTO Spicule LTD > t...@spicule.co.uk > > http://spicule.co.uk > > GB: +44(0)5603641316 > US: +18448141689 >
