| Hi João,
Thanks for the feedback.It’s been a while since someone seriously looked at this so it’s much appreciated. It also makes you kind of the resident expert on the thing ;). So, in your judgement, are there things that really should be done to make things, I would say, consistent at least?
Thanks, Jaap
On 10/6/21 19:42, Jaap Keuter wrote:Hi,
Are those wmem / pinfo->pool changes completed? Would be nice if that was consistent before branching. Is dfilter stabilised already?
I don't really have a roadmap, I'm just taking a fresh look at the code for general improvements, bug fixing, learning and just maybe come up with some kind of formal specification. These are the things that come to mind.
Thanks,
Jaap
On 30 Sep 2021, at 23:29, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
Hi all,
I have the 3.5.1 release scheduled for next Thursday, October 7, but I'm wondering if we shouldn't create the 3.6 branch and release 3.6.0rc1 instead. Unless anyone needs to delay the 3.6 branch I plan on doing the following:
Oct 6 : Release 3.4.9 & 3.2.17
Oct 7 : Create the release-3.6 branch
Oct 8 : Release 3.6.0rc1
Oct 20 : Release 3.6.0 and wind down the 3.2 branch
Nov 17 : Release 3.6.1 & 3.4.10
___________________________________________________________________________
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
___________________________________________________________________________Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>Archives: https://www.wireshark.org/lists/wireshark-devUnsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
|
