we do it a bit differently z=bug fixes that cause no api breaks y=new functionality+small/easy-to-migrate api breaks (preferrably no silent failures) x=big api breaks/new radical concepts
-igor On 2/5/07, nilo de roock <[EMAIL PROTECTED]> wrote:
A few newbie questions: In my perception numbering works like x.y.z increase z for bug-fixes increase y for new functionality increase x when you break the API ( Java 6 is in essence still 1.6 ) Is this how versioning works in Wicket? WebbyDB didn't compile with 1.x ( it did with 1.2.4), should that be reported? How long will 1.x be maintained, once 2 is around? -nilo -- View this message in context: http://www.nabble.com/Question-on-1.3-vs.-2.0-tf3179142.html#a8821696 Sent from the Wicket - Dev mailing list archive at Nabble.com.
