the biggest thing holding up the release are a few missing iclas, working on that now.
-igor On 2/22/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* [EMAIL PROTECTED]: > Author: ehillenius > Date: Thu Feb 15 10:19:54 2007 > New Revision: 508062 > > URL: http://svn.apache.org/viewvc?view=rev&rev=508062 > Log: > > damnit Johan I told you NOT to turn this thing on by default! We > just had a nice error on our production system. Thanks. DO NOT > TURN THE FRIGGIN' THING ON PLEASE. Instead, just ask people > (like me) to test and they will surely help out. Dear Eelco, Please mind your tone. Anyone depending on the current svn must be prepared to live a dangerous life. For my projects, I maintain a local patchset against an older Wicket snapshot, in order to avoid regression issues, and only integrate a controlled set of changes. With the code repository, it might happen that things work one day and are broken the other day. Production systems definitely don't like that. That being said, I'm worried by the current refactoring WRT serialization. When using latest SVN we have a lot of NotSerializable errors logged in the console. And even when launching the tests. And strangely enough that happens even without the custom serialization (WicketObjectOutputStream). With such refactorings, the hope to have Wicket 1.3 one day seems to vanish. We discussed to release in January, now it will be at least March. Why not do those refactorings in trunk, to be able to release on a fixed schedule and honor the old saying «release early, release often»? -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
