Hi Hans,
hdockter wrote: > > 1.0 means also our vision and what Gradle stands for is implemented. > I'm optimistic that with Gradle 0.3 we are fully competitive > regarding all major features to for example Maven. We might as well > call such a release 1.0. But in our vision there are features that go > beyond what is offered by build tools today. And only when they are > implemented we want to call it 1.0. > I think that Gradle offers a good feature set today. I also think that version numbers are important for companies when choosing a tool. It will be hard for a manager to choose a build tool that is in version 0.3. Even for open source projects, I think the reaction to seeing a 0.x version is "Let's look at it again in half a year". Also, look at Ant: it became mature only in version 1.6 (and even then, it didn't have Ivy). Beyond version number, a large set of plugins is important. It creates a feeling that many use cases have been answered. Ittay -- View this message in context: http://www.nabble.com/Roadmap-tp17752996p17753658.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
