Sure for releasing.. Did you also note that theres still issues with rendering the exception page when using ajax? Also mentioned in 3142<https://issues.apache.org/jira/browse/WICKET-3142>
<https://issues.apache.org/jira/browse/WICKET-3142> <https://issues.apache.org/jira/browse/WICKET-3142> 2010/10/29 Pedro Santos <[email protected]> > I'm just concerned about the side effects. A bug on the component data > index > can cause URL issues. For instance an URL generated for one behavior > invoking another behavior on the same component. Then we will have > developers evaluating the milestone and returning different problems than > the one reported by Nino. But I'm ok releasing the milestone with a note > explaining the possible issues. > > On Fri, Oct 29, 2010 at 1:32 PM, Jeremy Thomerson < > [email protected] > > wrote: > > > On Fri, Oct 29, 2010 at 7:12 AM, nino martinez wael < > > [email protected]> wrote: > > > > > I want change my vote to -1 until this is fixed : > > > > > > https://issues.apache.org/jira/browse/WICKET-3142 > > > > > > > Nino, > > Thanks for finding and reporting this issue, and thanks to Pedro for > > follow-up comments on it. I'd just like to reiterate that this is a > > *milestone* release; meaning: take it and break it. Experiment with new > > features and find bugs. In other words, if pages didn't render, that > would > > be large enough to stop a milestone release. But, minor bugs such as > this > > and the one I found when releasing it should not stop a milestone release > > from getting out there to test. > > > > If this were a bug on a release candidate, I'd say yes, stop it. But on > a > > milestone? Doubtful. We can build another milestone every week if > someone > > has an hour or so to do it. I can probably build M4 late next week. > > > > -- > > Jeremy Thomerson > > http://wickettraining.com > > *Need a CMS for Wicket? Use Brix! http://brixcms.org* > > > > > > -- > Pedro Henrique Oliveira dos Santos >
