On Mon, Aug 29, 2011 at 6:28 PM, tetsuo <[email protected]> wrote: > non-binding > > -1 to independent module versioning. I don't want to have a compatibility > matrix like Hibernate's ( > http://community.jboss.org/wiki/HibernateCompatibilityMatrix). > > +1 to semantic versioning (http://semver.org/) > > -1 to jump to 6.0, unless it features some major architectural change like, > make Wicket mostly stateless or something like that. Even with that, I'd > prefer to go with 2.0 instead. Large numbers, for me, indicate bloat (with > the exception of Chrome, because we don't even care about the version number > anymore) and instability.
if we followed simver from the beginning the next version would be 6.0.0, so what is the difference? -igor
