On Mon, Oct 1, 2012 at 3:20 PM, Martin Grigorov <[email protected]> wrote: >> 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!
We have tested our application with 6.1 and didn't uncover anything. We run stock tomcats and jettys, so I don't think it is a major issue, at least not a critical one (though the issue is reported as critical). > 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. We are not ignoring it, but assessing whether it warrants delaying the other 20 issues that were solved. > 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. Martijn
