On 3/26/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > I really don't understand what's the big deal here.
The big deal is that there is a big discussion, and suddenly the change is committed. Don't we have a process for changes that are controversial, perhaps not for you, but for other committers (like me)? Is it really *that* hard to just break out of the discussion, write up a small proposal that summarizes the discussion, and see if that goes through? Or do we have to monitor the svn commit logs to check if no unwanted changes go in? Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------- 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
