| From Vaughan Johnson <[email protected]> | Fri, 09 Mar 2012 17:35:02 -0800 | Subject: [Audacity-quality] ~36 hours?! (was Re: website update mockup & 2.0 release) > On 3/9/2012 3:03 PM, Gale Andrews wrote: > > > > | From Vaughan Johnson <[email protected]> > > | Fri, 09 Mar 2012 00:34:40 -0800 > > | Subject: [Audacity-quality] ~36 hours?! (was Re: website update mockup & > > 2.0 release) > >> I'm fine with another approximately 48 hours release review. Are we good > >> for finalizing 2.0 release by 23:00 GMT on March 10? > >> > >> After all this time, and last minute (for 10 days!) alarms, are we good > >> for that? Would March 11 be more comfortable? Let's get on with it. > > > > I think I'm OK with 23:00 UTC/GMT (current 23:00 in UK): > > http://www.worldtimeserver.com/current_time_in_UTC.aspx > > > > on March 10th from web sites' perspective. > > > > But are we fixing the build issue on upcoming Linux distros: > > http://bugzilla.audacityteam.org/show_bug.cgi?id=484 ? > > > > If so, does that need a 24 hour (or any) cycle? > > > > I thought it was agreed P3... Not? > > It requires a full round of rc's (not just tarballs), right? > > I'm okay with another 24 hours (though grinding my teeth...), as there > are still pending questions. March 11, 23:00 GMT?
Your last comment that I can find was "Seems to me we need to apply this patch and do another rc. Any disagreement? ". Short: I'm going to "suggest" as this is causing unease and we've gone back on the schedule already, maybe we should try to fix it by doing a 24 hour tarball rc on the 10th at 23:00 UTC/GMT. Longer: I've "suggested" the issue would probably be a P3 (now) if not fixed. Often these issues go in at P4, then (usually) get noticed/fixed when release time approaches. If this remained unfixed when Ubuntu 12.04 et al started releasing, it would have to become a P2, treated strictly. So you could take the simpler route and call it P2 now and be done with it. David has an alternative solution on the table which we have to consider (removing the include). I am not the best person to ask what a fix needs in terms of testing, but I would think it would need 24 hours' testing on a new tarball rc. Could we do a new one by 23:00 UTC/GMT on the 10th? The code in question is wrapped in: #if defined(__WXGTK__) && defined(HAVE_GTK) #endif so I can't (in my ignorance) see why it affects anything other than Linux. Gale ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
