On 3/9/2012 11:05 PM, Michael Chinen wrote: > On Fri, Mar 9, 2012 at 8:03 PM, Michael Chinen <[email protected]> wrote: >> On Fri, Mar 9, 2012 at 7:32 PM, Gale Andrews <[email protected]> wrote: >>> >>> | 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? ".
Well, no, my "last comment" was "I thought it was agreed P3... Not?", as you quote. New information came in, so I thought it less urgent. >>> >>> 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. Well, 24 hours after your message (7:32 PM PST) is past 23:00 UTC on March 10. Let's just accede to 23:00 UTC March 11, as there are open questions. >>> >>> [...] >> >> If the release manager says we should do the new linux rc I can commit >> the patch (David Timm's looks good) do a new one and put it up by then >> if I have 1-2 hours notice. > > FYI I just built the tarballs and tried them out. It builds an runs fine. > > Also, as Gale said, since this change is wrapped in #ifdefs for wxGTK > this should only affect linux rcs. Mentioning in case we are willing > to desynchronize the linux rcs once again and not do the windows/mac > rcs. Michael, that's excellent. Thanks for jumping on it and clarifying. Very glad it's just Linux rc's. Please go ahead and post those, and we'll not do the win/mac rc's. And target 23:00 UTC on March 11 for release! Thanks to all of you! - 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
