We thought it was mature enough to put out a 1.0 version, meaning that it provides basic functionality, and is robust enough to build production sites with. After that, we started working on 1.1, which basically has the features we think are important to make Wicket really good, and has some refactorings that resulted from new insights we gained from this list etc.
Whether you think it is mature enough depends on what kind of organization you are in, and what you're criteria for maturity are. As you can see from the list/ issue database, most bugs are not crucial things, but minor glitches and inconveniences. We waited for months before we even went in the RC cycle, and we are committed to quality above just quick functionality. I think the high level idea of immaturity usually comes from Wicket being new and 'unproven', not having great documentation - though as I mentioned before this week, Wicket's javadocs are better than a lot of other projects, including direct compatitors. JavaDoc is no replacement for good documentation, but with a proper IDE it helps you a lot finding out how to use an API. My opinion/ short roadmap for Wicket: 1.1. will be finalized within say two months. I view Wicket 1.1. as the first release that is really compatitive. It will still be a project that is mostly interesting for the experienced developer crowd though. But I think that will change when the wicket-stuff project mature, and when we fill in all the 'nice to have' feature we plan for Wicket 1.2 (though portlet support is more important than that). My hope is that Wicket will arrive somewhere beginning 2006. We need a couple of months to reach 1.2., write a book, write a good online manual etc. And we need a couple of months just to let our user base grow more. Growth has been steady, and we have all the reasons to believe it will stay that way. Eelco On 8/22/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote: > #: David R. Heffelfinger changed the world a bit at a time by saying on > 8/21/2005 10:24 PM :# > > Hello, > > > > I just finished posting a Wicket review/tutorial on my web site. I > > would like to get some feedback on it. If some wicket users could take > > a look and let me know how it can be improved I would really appreciate > > it. The URL is http://ensode.net/wicket_first_look.html > > > > Thanks, > > David > > > > Hi! > > I have passed through the tutorial and it is very interesting. > However the feeling I got after finishing it was that Wicket is not enough > mature yet, while for > being around the ML for a while and taking a quick look at the source the > impression was that it is > a mature product under heavy development (causing maybe some inconsistencies). > > What is the impression of other users/observers of the project? > > :alex |.::the_mindstorm::.| > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
