Thanks, Peter. I'll await consensus on WASAPI, but I think we already know the functional results either way, and it's good that the Manual changes would be small.
- Vaughan On 2/12/2015 3:14 AM, Peter Sampson wrote: > Hi Vaughan, > > Manual: readiness update > > as of this morning the only P1 issues remaining in the Manual > are those that relate to full WASAPI versus loopback-only WASAPI. > > If we revert to loop-back only then those P1s disappear and the Manual > stands ready for 2.1.0 - if we keep full WASAPI on, then I have a small > amount of work to update three pages in the Manual with comparatively > minor changes (flagged with the P1s). > > Further to an earlier email of yours I have just sent out an urgent email > to -quality to establish a consensus on WASAPI for 2.1.0 > > Cheers, > Peter. > > Peter Sampson > Tel: +44 (0)1625 524 780 > > ------------------------------------------------------------------------ > *From:* Vaughan Johnson <[email protected]> > *To:* Audacity Development <[email protected]>; > audacity-quality <[email protected]>; Audacity > Translation List <[email protected]>; For > discussion of Audacity Manual <[email protected]>; > Audacity Team <[email protected]> > *Sent:* Thursday, February 12, 2015 8:50 AM > *Subject:* Release Manager announcing GUI freeze for the Audacity 2.1.0 > release > > Hi, Audacity contributors. > > As Release Manager, as I pre-announced, I'm announcing GUI freeze for > the Audacity 2.1.0 release now (a few hours later than intended). > > This is per > http://vjohnson.users.sourceforge.net/Audacity_2.1.0_release_agenda.pdf > <http://vjohnson.users.sourceforge.net/Audacity_2.1.0_release_agenda.pdf> > steps 2.1.1 and 3. > > (Also at > https://code.google.com/p/audacity/source/browse/archives/release_process/release_agendas/Audacity_2.1.0_release_agenda.pdf). > > > > > It means the code for Audacity 2.1 is now allowed to change only for > things that do *not* affect the GUI. Audacity Manual authors and > translators can complete their work, and that will "typically be 5-7 > days", so that we can start building Release Candidates. I'd like > updates on readiness of those. > > > Thanks for all your contributions! > > - Vaughan > > > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
