I would second waiting for 5.12.5. Waiting for 13th is a little bit too much 
superstition for me though ;-)

5.12.5 fixes some issues we have with the UI

Regards
Roland

> Am 06.09.2019 um 07:43 schrieb Pascal Quantin <pas...@wireshark.org>:
> 
> Hi Jaap,
> 
>> Le ven. 6 sept. 2019 à 07:36, Jaap Keuter <jaap.keu...@xs4all.nl> a écrit :
>> I think you’re right Pascal, let it soak for a while to see if there are any 
>> showstoppers reported. We can pick it up whenever we want/feel that it’s 
>> good enough.
>> I would propose to push back the maintenance releases to next week, say 
>> Friday Sept. 13th? That should be okay right ;)
> 
> 
> As indicated yesterday I already updated our  bundled Npcap (and so far 
> nothing popped in their bug tracker).
> We might delay the release a bit to wait for Qt 5.12.5 though. It's 
> availability is currently planned for the 10th of September.
> 
>> 
>> Jaap
>>  
>> 
>>> On 5 Sep 2019, at 21:28, Pascal Quantin <pas...@wireshark.org> wrote:
>>> 
>>> Once in the past I updated Npcap right after the release of a new version 
>>> and we packaged a version that broke BPF filters. It was suggested by that 
>>> time that we should wait a bit to confirm that no blocking issue (like a 
>>> BSoD for example) pops, which seemed a conservative but still good 
>>> approach. I was not saying that we should wait weeks, but one day or two.
>>> Anyway as I intended to update it in the coming days I will do it now as 
>>> there seems to be a strong push.
>> 
>> ___________________________________________________________________________
>> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
>> Archives:    https://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>              mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to