On Tuesday 02 October 2012 10:36:07 Martijn Dashorst wrote: > On Mon, Oct 1, 2012 at 3:20 PM, Martin Grigorov <[email protected]> wrote: > > 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. > > It doesn't hold the vote, but I do want to make sure this isn't as > critical as the reporter states. That our application doesn't suffer > from this issue doesn't mean it isn't serious. > > I am unfortunately not in the position to debug it: my allotted time > for wicket was spent building the release. > > What about the following: > > Unless anyone confirms that > https://issues.apache.org/jira/browse/WICKET-4789 is critical in 24hrs > we release 6.1. If/when a fix surfaces in the next 2 weeks, I create > 6.1.1, we release that.
This sounds like a very good idea. From what I can see in the ticket, it is most likely related to mounting pages on urls ending with /, perhaps in combination with jsessionid, but the / part is essential. IMHO, this is not critical. Best regards, Emond
