Hi Jürgen, On Thu, Aug 09, 2012 at 01:33:29PM +0200, Jürgen Schmidt wrote: > I would like to propose now a new snapshot build based revision > 1371068 (tel:1371068).
-1 Didn't the last build show us that it is really a bad idea to propose one build just because there is a fix for a release blocker? Browse the archive looking for the rev. number to get a timeline idea: 1367440 1367911 1368799 1368968 1369110 1369843 A small resume: Rob's finding the missing update setting, Josef finding two issues on Sunday, even before the RC was announced on Monday; a new RC for those two fixes on Tuesday; now there is a fix, so yet another RC... What if another release blockers are found tomorrow? Yet another RC on Friday if the fix is available? In the meantime, I propose https://issues.apache.org/ooo/show_bug.cgi?id=120518 https://issues.apache.org/ooo/show_bug.cgi?id=120389 Crash bug 120389 has been reported on 2012-07-27, nobody notice it until the user made some noise. This shows that something is really not working with the way RC are proposed right after a fix is found for a release blocker, IMHO there should be enough time (a week, for example) to test the RC, even if a release blocker is detected, because nothing prevent this from finding another release blocker. Regards -- Ariel Constenla-Haile La Plata, Argentina
pgp8E9YWQCDdu.pgp
Description: PGP signature
