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? - V ------------------------------------------------------------------------------ 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
