P3s 198 and 202 look closable as resolved

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

P3s 198 and 202 look closable as resolved

Peter Sampson-2
Hi Gale,

it looks as though bugs nos. 198 nd 202 could be marked as resolved:
http://bugzilla.audacityteam.org/show_bug.cgi?id=198
http://bugzilla.audacityteam.org/show_bug.cgi?id=202

They are O3s and thus would otherwise need mentionin in the Release Notes, which
is not sensible if you agree that they have been fixed.


The P4s 1049 and 1208 look to be markable as resolved too.

Cheers,
Peter

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|

Re: P3s 198 and 202 look closable as resolved

Gale
Administrator
Thanks, Peter.

I started looking at 198 (Snap To) several weeks ago then ran into
some residual questions I wanted to ask about, enh I think, or
perhaps nothing we want to track. I couldn't wrap it all up in time when
I was looking at it, so I'll have to retrace my steps.

There are a lot of possible scenarios involved in bug 202. I read the
comment trail after Richard made his last comment, and I don't think
these comments have been verified as fixed:
http://bugzilla.audacityteam.org/show_bug.cgi?id=202#c5
http://bugzilla.audacityteam.org/show_bug.cgi?id=202#c25

I think this means at the very least that the release note needs strongly
watering down or perhaps I may think any residuals are P4.

Of course I would like no P2/P3 issues that are really resolved to appear
in the release notes, but bug 1567 testing has cost me a very great
amount of time as you can imagine.  I aim to resolve as many as possible
of the DEVEL-FIXED P3 or higher by release time but there are other
release notes that may need modifying or adding.

So I think this time it would be better if I copied over the release notes
into http://wiki.audacityteam.org/wiki/Release_Notes_2.1.3 . I'll let you
know when I've done that. It will probably be very close to release time.

If there are any DEVEL-FIXED you (Peter) have not yet flagged as fixed
but could do so that would help. Among P3 or higher I see:

http://bugzilla.audacityteam.org/show_bug.cgi?id=1314
http://bugzilla.audacityteam.org/show_bug.cgi?id=878
http://bugzilla.audacityteam.org/show_bug.cgi?id=1083
http://bugzilla.audacityteam.org/show_bug.cgi?id=923 .

I am not setup for JACK on Linux or Mac, and JACK would have a
time-costly learning curve for me, so
http://bugzilla.audacityteam.org/show_bug.cgi?id=56

is likely to stay on DEVEL-FIXED in near future. If Steve could
review that bug's release note or comment further, that would help.


Thanks,


Gale


On 11 February 2017 at 18:06, Peter Sampson
<[hidden email]> wrote:

> Hi Gale,
>
> it looks as though bugs nos. 198 nd 202 could be marked as resolved:
> http://bugzilla.audacityteam.org/show_bug.cgi?id=198
> http://bugzilla.audacityteam.org/show_bug.cgi?id=202
>
> They are O3s and thus would otherwise need mentionin in the Release Notes,
> which
> is not sensible if you agree that they have been fixed.
>
>
> The P4s 1049 and 1208 look to be markable as resolved too.
>
> Cheers,
> Peter

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality