On 4/12/07, Leo Simons <[EMAIL PROTECTED]> wrote:
A release can be called wicket-incubating-DO_NOT_USE_THIS_CODE-this- is-a-legal-reasons-only-release-1.3.0-alpha.zip and we can take care to not publicize that we release things, but if it is a release, it still needs to be distributed to the general public. And then after that we can pull the release so it exists only on archive.apache.org. If we don't do it that way we all get very confused.
I'm catching up with this discussion a little bit late, but the result is very interesting for the Ivy community, so I'd like to be sure we aren't going to make any mistake. Indeed in the Ivy podling we are currently preparing a release, which I hope we'll be soon able to submit to the IPMC vote. We've called this release 2.0.0-alpha-1-incubating, since for us too it's primarily a release made to validate our release process and the legal part. We don't intend to promote the use of this release, since things will still change until the 2.0release, and we haven't done much testing and validation. But we will however make the release public, with ad hoc disclaimer about its state. According to what I read on this thread, I'm a little bit lost to know if we can continue on this way or if we should make a more stable release. Any opinion before we submit the release to the IPMC would be welcome :-) Xavier -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
