> If I remember correctly, I believe non-ASF release artifacts have to be
hosted externally (i.e. not on ASF hardware).
Sounds good. They will be.
Thanks all!
On Fri, May 6, 2016 at 11:07 AM, P. Taylor Goetz wrote:
> If I remember correctly, I believe non-ASF release artifacts have to be
> hos
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 r
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 externa
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 A
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 tic
