FWIW, I'm going to hold off on spinning RC7 until Erlend signs off on RC6 in it University of Oslo Resin environment. Hopefully that should be sometime this weekend.
Karl On Fri, Jan 25, 2013 at 9:31 AM, Karl Wright <daddy...@gmail.com> wrote: > Agreed that we aren't shooting for perfection. Absence of significant > regression is the best we can hope for. ;-) > > Unfortunately, due to the significant amount of refactoring that took > place in this release, we're still discovering exactly where the > bodies lie. But I think we are getting close. > > Karl > > On Fri, Jan 25, 2013 at 8:42 AM, Jukka Zitting <jukka.zitt...@gmail.com> > wrote: >> Hi, >> >> On Fri, Jan 25, 2013 at 3:35 PM, Karl Wright <daddy...@gmail.com> wrote: >>> I've pulled up this fix to the release branch, and the vote on RC6 is >>> canceled. However, can everyone do at least a preliminary smoke-test >>> evaluation of RC6 at this time, and not wait for the "final" vote? We >>> aren't going to converge if we all keep waiting to do the evaluation >>> until we think there are no more RC's likely. >> >> No software is perfect and it's always possible to cut more releases >> to address issues as they come along, so in general I'd recommend >> people not to vote -1 because of each individual bug they encounter. >> >> As long as the code compiles, passes the existing test suite and has >> no other major issues (known security vulnerabilities, licensing >> problems, etc.), it should be ready to release. Smaller issues like >> CONNECTORS-622 can and IMHO should be fixed in the following release >> instead of holding up the current one. >> >> It's better to release early and often than to wait for perfection. >> >> BR, >> >> Jukka Zitting
