Hi Xavier,
On Jun 10, 2008, at 7:34 PM, Xavier Hanin wrote:
On Tue, Jun 10, 2008 at 1:58 PM, Ittay Dror <[EMAIL PROTECTED]>
wrote:
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.
I agree, a version number has a deep psychological effect. Call
your versions milestones with sub numbers (eg 1.0-Mx.y instead of
0.x.y versions) and you will attract more users than with 0.x.y
version scheme. Beta can be good as well.
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
But it still pull the heavy legacy load of being backward
compatible with 1.0. So if you really want to ensure backward
compatibility in 1.x stream, don't release 1.x too early. Or you
could simply target 2.0 as the mature killer version, 1.0 being
used to attract people and increase the number of plugins. With Ivy
we released a 1.0 pretty early, sometimes I think more time would
have been needed to get a better maturity, but maybe Ivy wouldn't
be where it is today without the increase in user number we've seen
with 1.0.
Thanks a lot for sharing your experience with Ivy. As you and Ittay
have proposed, it might be an alternative approach to use 1.0 as the
'fully competitive' flag and 2.0 for most of the major new features
we have in mind. We have some time to make a decision.
- Hans
My 2c.
Xavier
(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
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
