Re: [Audacity-devel] 1.3.13rc3 freeze
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale (A. Team) <ga...@au...> - 2011-04-09 04:20:38
|
Vaughan wrote: >>On 4/7/2011 4:21 PM, Gale (Audacity Team) wrote: >> 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. OK we only have rc3's present now for 1.3.13. > 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. That sounds fine to me if Manual Team are clear they have to stop by the next rc freeze. And RM has to decide if the Manual issues presented to him are "P2". I'd lobby that some of them are "P2" for the Manual we now have in rc3. Plus the ANSI/Unicode Win Manuals in rc3 are very slightly different (don't know about Mac). I hope this will all be better next time and that we can keep the Manual up-to-date in the first place. >> 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? The rule is to "release note" if P2 or P3. > Why would a release note change require rebuild? I thought that problem > with README changes needing rebuild was solved already by posting to web. Sorry, had my mind more on the old system. Release noting this as a bug this wouldn't "require" rebuild, for sure. But to make the issue "more visible" there's a good case (if we rebuild anyway) for noting the issue in the "Changes" for Device Toolbar (as a need to use the mouse). Listing a bug in the Changes has worked well to cut down reports before, so might be sensible if the bug stays at P2 (meaning it will only be in 1.3.13). I think the consensus so far in the bug report (regression on 1.3.12, VI issues) is for P2. Thanks, Gale -- View this message in context: http://audacity.238276.n2.nabble.com/1-3-13rc3-freeze-tp6247268p6256115.html Sent from the audacity-devel mailing list archive at Nabble.com. |