On Thu, 2008-07-17 at 19:43 +0200, Emmanuel Bourg wrote: > I wouldn't push for a 2.0 release in the current state, I'm not > convinced by the design of the new API. It seems more reasonable to > stabilize the 1.x branch before considering a major refactoring with CLI2.
Given that there is no rush of people to get involved in reviewing and picking up and progressing the 2.x branch, it does seem far more appropriate to progress the 1.x branch as far as possible. Get 1.2 out asap and then plan for a 1.3. As far as I can see changing from 1.0 to 1.2-SNAPSHOT does not cause any problem for the Groovy build and test. However, it seems that no unit tests were added for the problems raised by 1.1 so I cannot present evidence that 1.2 solves the problems. What I can say is that it doesn't create new ones. -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
