Re: [Audacity-devel] 1.3.13rc3 freeze
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Vaughan J. <va...@au...> - 2011-04-08 01:38:31
|
On 4/7/2011 4:21 PM, Gale (Audacity Team) wrote: > Vaughan wrote: >>> The Google Code downloads page is a mess with rc1's, 2's and 3's. Shall >> I >>> remove the old ones as usual, and note to do this on >>> http://wiki.audacityteam.org/wiki/Release_Process#Release_Candidates? >> I'd like to avoid lots of cross-editing on that page while I'm RM. And I >> have some exceptions to some of the changes that have been made since my >> major edit. Will get to those later. > OK, but what policy would you like on only having the current rc up on > Google Code? In past releases I just deleted the old ones straight away > without anyone objecting. Yes, I'm fine with that and will document it. Please delete them. Thanks. > > >>> However Ed has a point in that if we don't freeze the Manual, then >>> Win/Mac >>> packagers could pull slightly different versions of the Manual. We have >>> that >>> issue now in that the Extended Import Preferences are incomplete in >>> Martyn's >>> builds and a bit less incomplete in mine, and could be different again in >>> Leland's. >> I did not know about that. Aren't you all building from the same >> code?!!! That's what "freeze" means! > Of course, we're all building from the same source code. But if the Manual > is quite badly behind the code at start of rc1 which was true this time, and > allowed to catch up during the code freeze, then slightly different versions > of the Manual could be pulled according to when someone starts to build > (without e.g. someone pulling the manual and saying this is the one we're > building with). That's exactly why I said the freeze schedules should be synchronized, and the manual frozen for each rc. Yes, if the manual changes during the rc freeze, nothing will break, but it's relative chaos unless it freezes again at the next 48-hour freeze deadline. I'm open to work on "P2" manual changes in that 48-hour cycle if they can be completed before the next rc freeze. > > Another problem - bug 350 which Bill reported as PX a day or so ago: > http://bugzilla.audacityteam.org/show_bug.cgi?id=350 > > This is a hard one to rate. If you have selected in the Device Toolbar then > used the Play or Record shortcut, all other shortcuts are blocked. Most > people would figure out to hit Stop sooner or later, but it's an > embarrassment (IMO) and (I figure) a major problem for VI users as I can't > see how they get out of it unless they can deliver a click somehow. So at > the moment I have it as P2. That doesn't mean we have to fix it now, but it > would be hard (IMO) not to release note it (which means P3) and then that > requires rebuild anyway. I think it's a P3. But shouldn't the "release note it" rule be for P3 or higher? Why would a release note change require rebuild? I thought that problem with README changes needing rebuild was solved already by posting to web. - Vaughan |