If I remember correctly, I believe non-ASF release artifacts have to be hosted externally (i.e. not on ASF hardware).
When we had to do this for Storm, we added the following note to our download page: "NOTE: The following releases are neither a top-level Apache releases nor Apache Incubator releases. They are not endorsed by the Apache Software Foundation, nor hosted by Apache.” -Taylor > On May 6, 2016, at 12:45 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > > If you need a release before being ready for an Apache release, an > old-style non-Apache release is a fine thing to do. > > Also, keep in mind that the purpose of first Apache release is to iron out > process and IP issues. It should not necessarily intended as a full quality > release. So while an external release may be necessary for product and > quality reasons trumping Apache process, you should also push forward with > an Apache release with less than normal regard for product and quality. > That will mean that you will be ready when the project is ready to put out > a qualified release to also make it be an Apache release (incubating). > > The fact that quality/bugs/features and Apache IP checking are essentially > orthogonal issues is often not obvious to incoming projects. > > > > On Thu, May 5, 2016 at 6:22 PM, Shane Curcuru <a...@shanecurcuru.org> wrote: > >> Chris Riccomini wrote on 5/5/16 6:26 PM: >>> Hey all, >>> >>> Airflow was in the middle of a release prior to joining Apache Incubator, >>> and had several RCs out. The release has already been delayed by several >>> weeks due to bugs we've discovered. We don't want to tie this release to >>> the full-blown Apache release cycle, since we're not yet ready to tick >> off >>> all the boxes there. Is it possible for us to finish off our prior >> release >>> outside of Apache (i.e. tag it in Git, and put a package in PyPI)? >>> >>> Cheers, >>> Chris >> >> I don't see why not. Just don't call it an Apache project or release - >> call it whatever you used to call it, using whatever release platform >> the project used in the past. >> >> You can certainly email the dev@ list noting the release, just clearly >> noting that it's a release outside of Apache. >> >> All the code is open source licensed, so people are free to use it as >> they wish, just not using "Apache" with it (yet). >> >> - Shane >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
