I'd like to propose that we freeze the codebase now so we can work on bugs over the next few weeks for a Release Candidate. This is quite critical timing NOW for people who have been promised that a mid-June or early July launch of a commercial product on Wicket would be workable. I know I am one such person, but I can also point to other such promises made by the dev team (myself, eelco, others) on this mailing list.
This said, I'm not so hell-bent on shipping that I'd argue for a freeze before fixing something that's truly important. But we do really need to wrap this up as soon as humanly possible so we can ship a FINAL product in just a few very short weeks. So, here's the vote: [ ] I'm ready to freeze the codebase for RC bug fixing. [ ] Hold your horses, we REALLY MUST (fill in the blank) ______ first. NOTE: If someone comes up with a good reason not to freeze, we can revote with that on the ballot. -- View this message in context: http://www.nabble.com/-VOTE--Code-Freeze-for-RC-tf3735383.html#a10455790 Sent from the Wicket - Dev mailing list archive at Nabble.com.
