On Fri, Nov 15, 2013 at 4:26 PM, Craig L Russell
craig.russ...@oracle.com wrote:
...I think Storm could do the same. There is specific interest in the
incubating Storm community
but not general interest in the wider Apache community...
+1
Another similar (but older) example is Wicket which
Also, if it's not an Apache release, it probaly should not be hosted and
listed at Apache to avoid confusion.
On Thursday, November 14, 2013, Ted Dunning wrote:
First few words should read A disclaimer ...
I blame a combo of jet lag and *really* slow net link. Not the guy who hit
send
Agreed. It will not be hosted or linked to from any Apache site.
On another thread on the storm dev list, I have an open question as to whether
or not it’s okay to announce it (with a disclaimer that it is not an Apache
release) on the Apache mailing lists dev/u...@storm.incubator.apache.org,
IIRC, JSPWiki had exactly the same issue when it entered the incubator.
There were a non-Apache release or two while it was incubating, using the
non-Apache package names, hosted on non-Apache servers and announced on
non-Apache mail lists.
Since it wasn't an Apache release, it was not
If you release as an Apache Incubator project, the disclaimer is required.
If you release as your prior project, with prior infra and procedures, then
no.
Note: you cannot release as an Incubator project unless you use Apache
procedures.
Cheers,
-g
On Nov 14, 2013 11:49 PM, P. Taylor Goetz
First few words should read A disclaimer ...
I blame a combo of jet lag and *really* slow net link. Not the guy who hit
send without proofing, of course.
On Fri, Nov 15, 2013 at 7:41 AM, Ted Dunning ted.dunn...@gmail.com wrote:
I disclaimer to clarify that the 0.9.0 release is neither an
