So perhaps it is easier to just say: put 'incubating' in every jar file you intend to release yourself, whether or not it is in a tarball. That would make it easier to get the release through the incubator PMC as well IMO (less questions and explanations about 'why does this not have incubating')...
There is no limit to warn the downstream users of incubating stuff. Martijn On Mon, Mar 30, 2009 at 4:08 PM, Todd Volkert <[email protected]> wrote: >>> The downstream user must not be confused and really be aware of that it is >>> not an endorsed Apache release. > >> We are definitely compliant with the first two issues. The last one is a bit >> vague, but it implies that we could be compliant simply by including >> "incubating" in the version we include in the JAR's manifest... > > Unfortunately, I think just having it in the JAR's manifest wouldn't > suffice, because downstream users won't go looking in there to see > what we included. Simply looking at the filename could give them the > impression that we're an endorsed apache release, which means we'll > have broken the intent of the law, if not the letter of the law. > > -T > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
