Gili,
I see where you are coming from. We /also/ want to ship RC3 as soon as possible. However, we have found several core problems which should be fixed before we go to 1.0. These issues are mainly internal to Wicket, but have great influence on usage patterns or on promised features (for instance clustering support). If the currently found issues aren't solved, I assure you that the whole community of the serverside, Javalobby, and java.net will turn their backs on Wicket and that is something nobody wants (perhaps Howard Lewis Ship ;-).
I am aware of these issues which is why I am not pushing for a release until they're fixed :) It would just be nice to have a list of "stuff to do before RC3" and "estimate release date". I don't mind if we modify the list or projected release date as time goes by. It would just be good to have so people outside the core team know what's going on. I do appreciate your hard work. Thank you!
As to the roles on the wicket team, if you have read the mailing list for a while, you can easily see who is doing what. I mainly focus on delivering the goods, and fix the occasional bug. Jonathan, Eelco, Juergen and Johan are the actual core developers, where Eelco and Juergen also contribute heavily on the Wicket-stuff projects, and other open source projects. Chris is our main clustering guy and is also our 'conscience' when our commits go sour.
Any chance we can update the contributors page to reflect this? It would help direct the right questions to the right people.
You know, this is an open source project. As far as I know, we provide quick responses to questions of our users. Sometimes an answer is easy to give, and then the answer follows quickly. Other times this is not the case. But we do this in our free time, and for the Topicus guys we provide additional support by /using/ Wicket on our projects. But this is not a free lunch!
Yes, I find that the team replies fairly quickly to questions posted on the mailing list and I am thankful for that. I just want to point out that the same is not true vis-a-vis the Issuetracker system. I've reported some bugs over the past few months and it would be good to know what the target milestone is for fixing them and which team member is going to be working on it.
The problem with the current "hands off" attitude is that no one seems to be taking responsibility for issues that don't interest them. By assigning developers open issues you ensure that they take ownership of it and will prioritize it in their queue of things to do. Unassigned issues are ignored.
I am fairly sure that with a little effort we can improve this situation. Thanks again for all your hard work!
Gili
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
