Hi, I've made some bigger changes in wicket-ajax.js lately. Mostly because of requests/tickets by Christian Oldiges. He is not subscribed to the mailing lists but he suggested in IRC to do beta4 because of this. My personal opinion is that the changes are stable enough for 6.0.0.final. The unit tests prove it. If there are more bugs we will fix them in 6.0.1.
Christian created also https://issues.apache.org/jira/browse/WICKET-4675 which requires quite a big change in both JS and Java code. Honestly I'm afraid of such changes, especially just before 6.0.0.final. If someone has a simpler solution for the described problem then please share it now, otherwise I suggest to leave this ticket for some future version. On Fri, Jul 27, 2012 at 12:44 PM, Martijn Dashorst <[email protected]> wrote: > I intend to no longer keep wicket 6 hostage to updating the website. I > am unable to find enough time to actually work on such a noble cause > before we should release 6. > > Therefore I propose I start the release building process tonight/this > weekend, or when I find a spare moment to wrestle with maven/git/gpg. > > Any objections? > > Martijn > > PS I have received a 3rd party design in my inbox. It hasn't escaped > my attention, but my personal life, a work project schedule are in > such a conflict that I am unable to attend to such suggestions. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
