Maynard, Chris skrev 2010-05-12 03:38:
Hi Gerald,
What of the patches that have been submitted but not yet checked in? I understand that it's time-consuming to review patches and that some of the submitted ones may need to be re-worked and not quite ready, etc., but a quick bugzilla search indicates that 111 bugs (~21% of them) have patches submitted as attachments, a good portion of them likely waiting for "review_for_checkin?". It would be nice if those patches that are ready for integration could make it into 1.4 or those patches submitted could at least be "grand-fathered" into the 1.4 branch so one wouldn't have to wait an entire year (or more?) until 1.6 for the patch to become part of the next stable release. It's one thing to not want to add new protocols or major changes to the stable release, but surely many of them are not "enhancement" bugs or major rewrites of the capture core and would be suitable for inclusion. No? What are your thoughts
I think any one on the dev list could help speed things up by helping
reviewing patches especially if they need rework.
Regards
Anders
on this?
Thanks,
Chris
P.S. Here's a very simple patch that would be nice (for me) to get added: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4722 :)
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Gerald Combs
Sent: Tuesday, May 11, 2010 7:41 PM
To: Developer support list for Wireshark
Subject: [Wireshark-dev] Wireshark 1.4
I'd like to create a branch for 1.4 in the next week or so and release
1.4rc1 soon after.
If you have added a new feature in the past year, please review the
release notes to make sure it's listed.
It would be nice if we could get capture triggers in the release. There
are a couple of patches in Bugzilla (2039 and 3967); I'll try to review
them soon.
I don't plan on maintaining the 1.0 branch after the release. If anyone
would like to take over maintenance duties, let me know.
