On Mon, Oct 1, 2012 at 4:02 PM, Martijn Dashorst <[email protected]> wrote: > On Mon, Oct 1, 2012 at 11:06 AM, Martin Grigorov <[email protected]> wrote: >> -0 >> >> Did someone tried to debug https://issues.apache.org/jira/browse/WICKET-4789 >> ? >> It is related to url-encoded jsessionid so it may not be a corner >> case. Maybe you didn't have problems with it because your app use the >> cookie based approach. > > But is it severe enough to hold back this release? If this bug hits > you (and cookie-less operation is important) don't upgrade to 6.1, but > wait for 6.2? > > I agree that it would be best to not release with this issue, but > there will always be issues, and if we wait for the perfect release, > we'll never get anything out of the door.
Sure. This is true. But then there is no point to test our apps for the voting. Just check that the voted sources can be build. Easy! I'm still -0 because this is a regression. We have stopped releases before when there were similar regressions found by us or by our users. By just ignoring such reports during the vote we discourage our users to give us feedback for the next release votes. The problem with FilterForm is not a new one, so I agree it can wait. 0 vote doesn't stop the release, right ? I don't want to veto the release because I wont be able to fix this soon. > > Martijn -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
