Hani Suleiman wrote:
> 
> The website lists m4
> 

Not sure whether you refer to the m4 release notes; everything else should
be back to m3.


Hani Suleiman wrote:
> 
> The downside of course is that the m4 documentation (for those foolish
> enough to have upgraded) is nowhere to be found (at least, I'm unable to
> find it from a cursory glance).
> 

>From http://www.gradle.org/documentation.html it should be fairly obvious
where the documentation is, because the URL structure is always the same. m4
is here: http://www.gradle.org/releases/1.0-milestone-4/docs/


Hani Suleiman wrote:
> 
> There's also no documentation on the website at all about the fact that m4
> was silently withdrawn or found to be unusable, nor is there anything that
> encouraged people not to use it.
> 

There was a post on the mailing list, and then everything was set back to
m3.


Hani Suleiman wrote:
> 
> Obviously releases go wrong sometimes (well, not often, but I guess it can
> happen). Usually this is followed very quickly with a fixed release, but
> it'd been over a week now with no updates that are visible to the casual
> user. I'm subscribed to this list, follow the twitter feed, and check the
> website, and am unable to get any sense of comfort from any of those.
> 

The problems in m4 come from a big and complex external contribution (which
we are very grateful for but released too early). So it's hard to say when
everything will be fixed, and it isn't entirely in our hands. 

If m4 works good enough for you, then stay with it (as I do myself). If not,
I recommend to go back to m3.

--
Peter Niederwieser
Principal Engineer, Gradleware 
http://gradleware.com
Creator, Spock Framework 
http://spockframework.org
Twitter: @pniederw

--
View this message in context: 
http://gradle.1045684.n5.nabble.com/Future-plans-tp4713783p4713990.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


Reply via email to