Re: [Audacity-devel] P2 bugs and Freeze Delay
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Peter S. <pet...@gm...> - 2016-10-13 10:20:46
|
In this freze delay, is there any chance that someone can spare a few moments to address the issues in the P2 bug http://bugzilla.audacityteam.org/show_bug.cgi?id=1427 and its associated Wording page in the Wiki http://wiki.audacityteam.org/wiki/Wording A couple of these wre logged as long ago as 2008, eight years ago and have lain untouched since then. The changes would seem to be relatively simple to do and should only take a few moments for someone with the right skills and priveleges. The only one we may want to leave for post-2.1.3 if the modernization of "program" to "application" - and note btw that this is a task that we are part way though so we have mixed nomenclature in this respect. Cheers, Peter On Wed, Oct 12, 2016 at 10:28 PM, James Crook <cr...@in...> wrote: > Gale is right that the release is technically blocked anyway because of > Mac not building. > > Any P2 can block release, and we have 36; I am also behind on getting > signing sorted; I'll be able to pay closer attention to Audacity in a > week's time, but it isn't wise to go into freeze at this juncture. I've > also got many things I need to catch up with that I have left to one > side to move Audacity forward, and I need to urgently clear those before > we freeze. > > --James. > > > On 10/12/2016 3:39 PM, Gale Andrews wrote: > > On 11 October 2016 at 09:39, James Crook <cr...@in...> wrote: > >> Original plan was to go into Freeze on 9th October. > >> > >> However, we have many serious P2 bugs (36), any of which RM could block > >> on. We also currently have issues that do not get recorded as bugs, > >> such as the patchy organisation of our patches to 3rd party libraries, > >> and (current) failure to build on Mac. Bug 437 > >> http://bugzilla.audacityteam.org/show_bug.cgi?id=437 which is P2, is a > >> blocker for release because it is reported on as a limitation/issue with > >> Audacity on the Wikipedia page. > > Leaving aside Wikipedia, the reported frequency of user impact of > > that problem is quite low. When this happens during recording > > it could (weakly) be argued as user error, because of the already > > existing Status Bar messages for remaining disk space. > > > > So I think in practice bug 437 is like bug 276 PulseAudio freeze. > > 437 would get moved to P1 at a time when we have the resources > > to fix it and the time to test the fix thoroughly so that new bugs are > > not introduced. > > > > If we are waiting for certification of the Win/Mac installers then it > makes > > sense to continue clearing P2's that RM thinks could block the release. > > Are we now making progress on certification? > > > > Note also that the release is technically blocked anyway. it does not > > build on Mac because of how the gcc 4.9 requirement has been > > specified. I suggest fixing that or people on Mac can't test new fixes. > > > > > > > > Gale > > > >> The patches to 3rd party libraries have > >> ballooned with work to work around wx3 issues in this release, so it is > >> important that we sort that out. > >> > >> The work on patches is important. If we don't do it, we're not helping > >> wxWidgets to improve the library we depend on. We need our own clone of > >> wxWidgets to be fully patched with all our patches. We need to document > >> the problems we've worked around: > >> http://wiki.audacityteam.org/wiki/For_Upstream_wxWidgets and > communicate > >> them upstream > >> > >> So, as RM, I'm deciding we're in freeze-delay. We will freeze later > >> than originally planned. When we get 437 sorted there will be a new > >> translation string. Other P2 bug fixes may do that too, so it is not > >> appropriate to sent the updated pot files to translators yet. > >> > >> I'll make a call as to when to move on to freeze later, rather than set > >> a specific date. We have to have made enough progress for it to happen. > >> > >> --James (with RM hat on). > >> > >> > >> ------------------------------------------------------------ > ------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot > >> _______________________________________________ > >> audacity-devel mailing list > >> aud...@li... > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > _______________________________________________ > > audacity-devel mailing list > > aud...@li... > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |