Hi, I think we are not too far to be able to make a first attempt at releasing 2.0 alpha 1.
My last questions are for some minor things I'm still wondering about: - I'd like to rename the CHANGES.txt file to CHANGES. Indeed, it's the only root documentaiton file with a .txt extension. Maarten, any objection? - shall we put this release on the maven 2 repository, and in this case, what do we need to do? I think making Ivy available on maven 2 repository would be a good sign of our integration, and would also help users who depend on Ivy as an external dependency. This last point is not critical for this release, since it's oly an alpha release, the API is still subject to change. So, I'm not sure if we should release this version on maven 2 repo... I'd really like to make this release soon, and there would be work to do to provide the release on maven 2 repository. But on the other hand, we need to provide an http accessible ivy jar, at least to update go-ivy example and ivy build itself, and it would be nice to use maven 2 repo for that. Any suggestion? - Xavier -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
