Personally, my preference is not so strong. Having a 2.0 version give the impression that it is a brand new implementation,with new idea, without backward compatibility. For a user of ivy, this is clearly not the case.
Also, I think that having a 2.0 followed by a 3.0 would not be a good sign of stability for the user. Now, it is true that it would mark to move to apache, and it is also true that the backward compatibility of the API has been broken. So, I don't know. This was the argument pros and cons I see. But which one to choose? I have no real prefference. Is there any apache conventions about version numbering scheme? Gilles 2007/3/23, Maarten Coene <[EMAIL PROTECTED]>:
I also prefer to use 2.0 as the next release version. Maarten ----- Original Message ---- From: Xavier Hanin <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, March 23, 2007 7:02:14 PM Subject: release preparation: is 1.5 the appropriate target revision? Hi, While preparing the next release I've started wondering if 1.5 is the appropriate target revision. Indeed, there have been major changes in the source code structure, and we even have renamed configuration files to settings files. More changes may come before the final release, including a new default public repository (we will certainly use maven 2 repository instead of ivyrep as default repository). Hence I wonder if we shouldn't use 2.0 instead of 1.5. This doesn't mean I'd like to include more modifications like the discussion about Ivy 2.0 was suggesting some time ago, but just to reflect the number of changes, and ease the separation between Jayasoft and Apache versions. Then the previous suggestions for Ivy 2.0 would still apply but for a 3.0 version. WDYT? - Xavier ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html
-- Gilles SCOKART
