The recent two dataloss bugs made the release of 1.6.2 rather pressing. However, I think we should still test the recent fixes before actually releasing 1.6.2, to verify the fixes did not introduce bad side effects.
So here is my proposal: * I'm gonna apply the patch for bug 5833 to branch and trunk in a minute. * I would like to urge you to stress-test branch for some days, if possible * Since I am offline next week (as of Tuesday), I'm gonna set up a tarball tomorrow and make it available to you. You can call this the release candidate of 1.6.2. * If no grave problems show up, this tarball will be 1.6.2. The advantage of the tarball is that packagers can already start to build the binaries next week, so we can release 1.6.2 immediately after my return, on next weekend, if no problems arise. Sensible plan? Jürgen
