For this particular release it would be nice to find any regressions before 3.2.0rc1. I tested a Windows build locally and didn't find any obvious bugs, but if we do run into issues I can release 3.1.2 tomorrow or Wednesday.
On 11/18/19 9:27 AM, Jaap Keuter wrote:
> Are we gonna give the new Qt a little 'soak time’ in the field before going all in on that one?
> Would be nice to prevent unexpected regressions.
>
>> On 18 Nov 2019, at 18:12, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
>>
>> On 11/18/19 5:53 AM, Maynard, Chris via Wireshark-dev wrote:
>>>> -----Original Message-----
>>>> From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On
>>>> Behalf Of Gerald Combs
>>>> Sent: Tuesday, November 12, 2019 7:12 PM
>>>> To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
>>>> Subject: [Wireshark-dev] 3.1.1 and 3.2.0 release schedule
>>>>
>>>> A few people at SharkFest asked when 3.2.0 would be released, and I'd like to
>>>> do so before the end of the year. Following from that I've tentatively scheduled
>>>> the following:
>>>>
>>>> Nov 14: Release 3.1.1
>>>> Nov 20: Create the master-3.2 branch
>>>> Dec 5: Release 3.2.0rc1
>>>> Dec 11: Release 3.2.0
>>>> Dec 16: Switch automatic updates to 3.2.0
>>>
>>> Qt 5.12.6 was released on Nov 13, and so it would probably be a good idea to include it in these upcoming releases, if time permits.
>>> https://www.qt.io/blog/qt-5.12.6-released
>>
>> Done, for the Windows master, master-3.0, and PD builders.
>>
>> I also plan on starting the 3.1.1 release process in about 20 minutes or so (between 9:30 and 10:00 am PT).
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
