>>> On 8/30/2008 at 12:25 AM, in message <[EMAIL PROTECTED]>, Carlo Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote: > On Fri, Aug 29, 2008 at 02:40:00PM -0400, Ofer Inbar wrote: >> Should this have made it into 3.1, or 3.1.1? It >> doesn't look like it. > > There is a fix in trunk now with r1738 and unless something goes wrong with > it, will be most likely released with 3.1.2 and 3.0.8. > > 3.1.1 is already in testing and since this bug is not a showstopper for that > specific release, I'd be surprised if the release manager decides it should > be backported to it, but that shouldn't prevent you patching your own > package > with the proposed patch if you don't want to wait. >
If we are confident enough that the patch for this bug solves the problem, then I have no problem scraping 3.1.1, tagging and rolling 3.1.2 and restarting the testing period. The whole point of the testing period is to flush out problems like this and then determine if the fix is important enough to retag and retest. We need some feedback on how serious this problem is and how confident we are in the fix. I would rather throw away 3.1.1 now in favor of a fixed 3.1.2 than half to do this all over again next month. Brad ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
