Re: [Audacity-quality] Testing fix-made bugs (and closing them)

[Peter S. <pet...@gm...>]

Tested changes on audacity-win-r12a2d06-2.1.3-alpha-28-jan-16 (since
preciods 17c9369)
all test ok on W10

1272  Mixdown export shows no progress if one or more tracks are much
shorter than the others
1282  Tracks > Stereo To Mono is not removed from menu if disabled in
Plug-in Manager but is disabled for session and crashes if used
1288  "Simplified" language no longer supported and crashes Audacity
1299 (tested By David Bailes) Track loses focus after applying a Chain to
the project
1169  Spectrogram scale range setting only applied for linear scale
1317  Description message is confusing in Analyze>Find Clipping
1306  Tracks > Align Tracks and > Move Selection when Aligning shortcuts no
longer work

Peter

On Thu, Jan 28, 2016 at 2:03 PM, Peter Sampson <
pet...@gm...> wrote:

> Tested changes on audacity-win-r12a2d06-2.1.3-alpha-28-jan-16 (since
> preciods 17c9369)
> all test ok on W10
>
> 1272  Mixdown export shows no progress if one or more tracks are much
> shorter than the others
> 1282  Tracks > Stereo To Mono is not removed from menu if disabled in
> Plug-in Manager but is disabled for session and crashes if used
> 1288  "Simplified" language no longer supported and crashes Audacity
> 1299 (tested By David Bailes) Track loses focus after applying a Chain to
> the project
> 1169  Spectrogram scale range setting only applied for linear scale
> 1317  Description message is confusing in Analyze>Find Clipping
> 1306  Tracks > Align Tracks and > Move Selection when Aligning shortcuts
> no longer work
>
> Peter.
>
> On Wed, Jan 27, 2016 at 3:04 PM, Paul Licameli <pau...@gm...>
> wrote:
>
>> Thanks, Peter!
>>
>> If you follow the steps to reporoduce for 501 in version 2.1.2, you will
>> see plainly wrong behavior when time-sihfting some clips vertically across
>> tracks.  I will say more in Bugzilla comments.
>>
>> PRL
>>
>>
>> On Wed, Jan 27, 2016 at 9:55 AM, Peter Sampson <
>> pet...@gm...> wrote:
>>
>>> As it appears that we seem to have consensus that the primary target for
>>> the 2.1.3
>>> release is to fix as many of the bugs as possible we need also to ensure
>>> that we on
>>> QA are as swift as the develpers by testing and closing (if appropriate)
>>> the fixes that
>>> they make.
>>>
>>> Otherwise we will find ouselves later down the road with an intimidating
>>> amount of bug
>>> fixes to test and evaluate.
>>>
>>> Paul and Steve have already put thir shoulders to wheel and have
>>> generated an committed
>>> fixes for a fair number of bugs - and Leland is preparing to take up the
>>> struggle.
>>>
>>>
>>> In order to assist this process I am preparing to allocate time to
>>> testing bug fixes on W10
>>> as soon as possible after they become available in a nightly.  This of
>>> course only tests
>>> on one Windows platform and I am not empowered to close bugs.
>>>
>>> The Bugs I have tested so far and that look to be good to go so far on
>>> W10 are{
>>> 1311  Description message is ungrammatical in Normalize
>>> 1312  Description message is wrong in Leveller
>>> 52     Truncate Silence should cater for the common use case of
>>> per-track operation
>>> 30     Transport shortcuts write label at cursor position when label
>>> track has focus
>>> 389    Left-click to merge a stereo clip can move other clips if track
>>> was made from mono
>>> 1307  Misbehavior pasting mono into stereo
>>> 1310  Expanding cutline in stereo channel leaves incorrect undo history
>>> 671    Crash when joining splits with mouse
>>> 389    Left-click to merge a stereo clip can move other clips if track
>>> was made from mono
>>> 1217  "Other uncompressed files" exports saved with incorrect extension
>>> 1239  Importing multiple files into new project windows produces
>>> waveform, but incorrect length on Timeline
>>>
>>> It's a fair list already but hopefully there will be many more to come
>>>
>>> A couple that are a bit beyond my skill level (and comprehension) are
>>> 501 & 955
>>>
>>> Cheers,
>>> Peter.
>>>
>>
>>
>