Re: [Audacity-devel] Audacity 3.0.2 Released

[James C. <jam...@gm...>]

On Mon, 19 Apr 2021 at 16:20, John Colket <jc...@gm...> wrote:

> Doesn't James get to celebrate first?
>
> Congratulations, James! ☺
>
> On Mon, Apr 19, 2021 at 11:11 AM Peter Sampson <
> pet...@gm...> wrote:
>
>>
>>
>> On Mon, Apr 19, 2021 at 2:31 PM James Crook <jam...@gm...>
>> wrote:
>>
>>> We've just released our Audacity 3.0.2.  Here's the release announcement:
>>>
>>> https://www.audacityteam.org/audacity-3-0-2-released/
>>>
>>
>> Well done James !
>>
>
It's well done everyone!  I get to write the release announcement, and
actually push the release up, but we wouldn't have got here without the
hard work of multiple people.  Jack's work on 2700 was crucial, the most
important single thing in 3.0.2.  Without it we'd have only had a release
with better diagnostics, and not the new code that fixes at the least the
case Jack was seeing of 2700.

It's a real cliche that this kind of thing is teamwork, but quite honestly
without multiple translators willing to get translations done quickly,
testing, retests, changes and bugzilla updates, documentation, help to and
collecting of feedback from users, and multiple coders working on the code
we wouldn't have got to here now.

So thanks to everyone.  We should be careful about celebrating.  If we
celebrate too loudly things have a habit of rebounding.  But we can be
collectively pleased/proud of having worked effectively together to make
something good for other people in Audacity 3.0.2.



>
>>
>>
>>>
>>> The freeze on code and strings and manual is now lifted.
>>>
>>> 3.0.3?  I am hoping/expecting we will get more of Paul's restructuring
>>> in, in 3.0.3, and that we will do something about the effects manager
>>> <https://bugzilla.audacityteam.org/show_bug.cgi?id=2452>.  I'll be
>>> perfectly happy if everything's a bit quieter than it has been for 3.0.0 to
>>> 3.0.2!  We do have GSoC moving into the second stage, so a quieter period
>>> is probably wishful thinking.
>>>
>>
>> For 3.0.3 (wearing QA hat) I would really like to see us sort this
>> proposal
>>
>> https://wiki.audacityteam.org/wiki/Proposal:_Rationalizing_where_new_tracks_are_created_to_aid_usability_and_consistency
>> Which has these two attendant bugs
>> *Bug 2219* <https://bugzilla.audacityteam.org/show_bug.cgi?id=2219> - ENH:
>> Add new track places the track at the bottom of the project - should be
>> under user control
>> *Bug 2220* <https://bugzilla.audacityteam.org/show_bug.cgi?id=2220> - ENH:
>> Duplicate command places the duplicate track(s) at the bottom of the
>> project -not under the selected track(s)
>>
>> Documented in
>>
>> https://wiki.audacityteam.org/wiki/Next_Release#Requests_to_the_RM_for_3.0.3
>>
>> The current behavior(s) annoy a lot of Forum posters over the years.
>>
>> Peter.
>>
>>
>>
>>> --James.
>>> _______________________________________________
>>> audacity-devel mailing list
>>> aud...@li...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>
>> _______________________________________________
>> audacity-devel mailing list
>> aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>