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-10 00:26:40
|
On 4/8/2011 9:20 PM, Gale (Audacity Team) wrote: > 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). Fair enough. But release-blocking for beta means P1 or higher, so these are not release-blocking. RM may allow them in an rc cycle, but the emphasis should be on release-blocking problems, if there are any. > > <snip>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. Good. Thanks. > > 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). I suggest putting the Changes section on the web, too. Have as little content as possible in the README. - Vaughan |