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
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 wrote:
>
> On 11/18/19 5:53 AM, Maynard, Chris via Wireshark-dev wrote:
>>> -Original Message-
>>> Fr
Hi,
I'm working on dissecting a proprietary protocol that extends Bluetooth HCI_ACL
with a LUA dissector. As there's no heuristics dissector list registered for
this particular protocol I thought something similar could be achieved with a
chained dissector. I retrieve the original HCI_ACL disse
On 11/18/19 5:53 AM, Maynard, Chris via Wireshark-dev wrote:
>> -Original Message-
>> From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On
>> Behalf Of Gerald Combs
>> Sent: Tuesday, November 12, 2019 7:12 PM
>> To: Developer support list for Wireshark
>> Subject: [Wireshark
> -Original Message-
> From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On
> Behalf Of Gerald Combs
> Sent: Tuesday, November 12, 2019 7:12 PM
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] 3.1.1 and 3.2.0 release schedule
>
> A few people at SharkFes
