On Mar 7, 2007, at 7:31 AM, Ryan Sonnek wrote: > Just my 2 cents, but considering the *massive* API changes in other > opensource projects when releasing a major version, i don't think > providing users with an easy "upgrade path" is that important. > > Look at struts for example. version 2.0 is a *complete* rewrite and > requires users to do a lot of work to change. But how many people are actually upgrading from 1.0 to 2.0? I don't think the number is very high precisely because of the massive API changes.
In general, I think frameworks that provide an easy upgrade path are far more successful. For example, Spring's 2.0 release is pretty much a drop-in replacement. Hibernate provided a fairly easy upgrade from 2 to 3. At the other extreme is Tapestry, which has lost a lot of users (including me), developers and overall momentum by rewriting every major version from scratch. I'm not saying that (especially open source) developers shouldn't make big changes, I'm just saying that the cost shouldn't be underestimated. > > I would rather have the wicket developers make these decisions based > on what's best for the Wicket API rather than what's best for users. > Just a thought... > Sure, but the developers are users too, so hopefully we all want more or less the same things. -Ryan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
