On Tue, Jul 26, 2011 at 4:48 PM, Hyrum K Wright <hyrum.wri...@wandisco.com>wrote:
> All, > 1.7.0-beta2 is out in the wild, and folks are testing it. I know > we're still fixing bug and STATUS is still a bit active, but how do > folks feel about starting the release candidate train? Or, if you're > uncomfortable with that now, what are your criteria for doing so? > I have been using 1.7 exclusively now on all systems. I am using it from Subclipse, command line and TortoiseSVN. I am very happy with it from my own usage and I would be +1 on a RC. I have not been following all of the items that have gone through STATUS. I know there have been a LOT of nice bugs and fixes caught and there will likely be more. But I do not recall any of the type that we would have had to overly rush to get a 1.7.1 out if they had made into a release. I personally think that Neon should be our default for 1.7 and would like to see us make that change. However, given that just about everyone that produces binaries for download seems likely to patch the code so that Neon is the default anyway, it is not something I am going to fight for. It might even give us the best of both worlds. Most users will still be using Neon but given that Serf is the default in the source code there will still be a lot more users using it and filing bugs. > > Reminder: small fixes can still go into the release branch after the > first release candidate, and be included in the final release. Only > critical (read: blocking) issues will restart the soak. > +1 -- Thanks Mark Phippard http://markphip.blogspot.com/
