On Wed, Aug 24, 2011 at 10:01 AM, Mark Phippard <[email protected]> wrote:
> This is total strawman that you are setting up just so that you can knock > it down. Hyrum has said on numerous occasions that he can and will merge > bug fixes prior to creating the final 1.7. As he pointed out in a recent > reply this was a safe fix that was reviewed. There was nothing that was > going to prevent this from going into 1.7.0. If you disagree with this > policy, then start a new thread for it. There are definitely going to be > bugs found in any RC we release. If we treat all bugs like this we will > never release. All we have really accomplished is to push this release off > another week. > >From the Community Guide: "At the beginning of the final week of the stabilization period, a new release candidate tarball should be made if there are any showstopper changes pending since the last one. The final week of the stabilization period is reserved for critical bugfixes; fixes for minor bugs should be deferred to the A.B.1 release. A critical bug is a non-edge-case crash, a data corruption problem, a major security hole, or something equally serious." http://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization -- Thanks Mark Phippard http://markphip.blogspot.com/
