Re: Wireshark 1.4

["Atcitty, Torrey" <torrey.atcitty () harman com>]

Gerald,

Do you have a specific hard cutoff date for patch submissions for the 1.4 release? I'm currently working on trying to 
get at least the main AVB (Audio Video Bridging) protocols integrated into the main branch and it would be great if 
they made it into 1.4. The reason being alot of major companies who are actively developing products using AVB are 
eagerly awaiting the submission of my dissectors so they can use them as well. I've submitted one just yesterday which 
looks good based on feedback I have gotten. Another one incorporates really minor changes into the existing 1588 
dissector (packet-ptp). And the final one is also a new dissector, but one my company has been maintaining for over a 
year now so it has also already been extensively tested. I'm asking because I want to know whether I should drop 
everything else and quickly get the outstanding two finished like today, or maybe by EOB Friday if at all?

Thanks,
-Torrey

________________________________________
From: wireshark-dev-bounces () wireshark org [wireshark-dev-bounces () wireshark org] On Behalf Of Anders Broman 
[a.broman () telia com]
Sent: Tuesday, May 11, 2010 10:46 PM
To: wireshark-dev () wireshark org
Subject: Re: [Wireshark-dev] Wireshark 1.4

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 () wireshark org [mailto:wireshark-dev-bounces () wireshark org] 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.


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://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:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe