A couple of the wicket committers lay out precisely what they tested (not each individual unit test, but what actions were done) and report that back in their vote. This has a couple of advantages: it shows what has been done, and provides guidance to others checking the release themselves.
So can you elaborate more on what exactly you did to confirm that this release is valid? Browsers used, builds ran, etc. Did you use the artifacts as provided by the downloadable distribution? Did you check out the tag, and build the release from there, and compared it against the distribution? Did you use the self build artifacts to check if they too work? Martijn On Fri, Apr 3, 2009 at 2:52 PM, Greg Brown <[email protected]> wrote: > Very good point. I have also performed a smoke test and reaffirm my +1 vote. > > On Friday, April 03, 2009, at 08:33AM, "Martijn Dashorst" > <[email protected]> wrote: >>I am glad everybody is on board for the release and voting happily. >>There is one caveat: you are voting on behalf of the Apache Software >>Foundation. Unless you actually looked at the release, confirmed >>everything is ok, the tests run, the build is repeatable, you should >>not vote +1. As a proposed Committer and PMC member you are expected >>to perform due diligence. >> >>A +1 vote carries a lot of weight. When I see +1's immediately >>following a vote request on a release, I don't see due diligence, but >>an anxious community to get a release out. >> >>Martijn >> >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
