Wireshark mailing list archives
Re: 2.5.0, 2.6, and 3.0 release planning
From: Roland Knall <rknall () gmail com>
Date: Sat, 3 Feb 2018 13:56:55 +0100
yes, those should be fixed before a 2.6 release. For 2.5 I think it could be ok. cheers Roland On Sat, Feb 3, 2018 at 12:52 PM, Jakub Zawadzki <darkjames-ws () darkjames pl> wrote:
Hello, W dniu 2018-02-02 23:45, Gerald Combs napisał(a):I think we've fixed the major issues identified by Stig, Jim, and others so I'd like to release 2.5.0 on February 6.In oss-fuzz queue currently there are few crashes, and one inifite loop. Should it be a blocker for a release? Regards, Jakub. ____________________________________________________________ _______________ 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-request () 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-request () wireshark org?subject=unsubscribe
Current thread:
- 2.5.0, 2.6, and 3.0 release planning Gerald Combs (Feb 02)
- Re: 2.5.0, 2.6, and 3.0 release planning Stig Bjørlykke (Feb 03)
- Re: 2.5.0, 2.6, and 3.0 release planning Jakub Zawadzki (Feb 03)
- Re: 2.5.0, 2.6, and 3.0 release planning Roland Knall (Feb 03)
- Re: 2.5.0, 2.6, and 3.0 release planning Alexis La Goutte (Feb 04)
- Re: 2.5.0, 2.6, and 3.0 release planning Roland Knall (Feb 04)