Wireshark-bugs: [Wireshark-bugs] [Bug 4665] NTLMSSP_AUTH domain, user and host truncated when NT
Date: Wed, 29 Dec 2010 07:13:54 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4665

--- Comment #3 from Chris Maynard <[email protected]> 2010-12-29 07:13:51 PST ---
(In reply to comment #2)
> I guess I thought only fixes for "serious" bugs (crashes, etc) were being
> backported to 1.2. Should this fix be backported to 1.2 ?).

Excellent question.  Looking at http://wiki.wireshark.org/Development/Roadmap,
there are currently 30 bug fixes scheduled to be back-ported to 1.4.3 (not
counting the optional value_string_ext bug fixes) but only 3 scheduled to be
backported to 1.2.14.

It's been sort of a guessing game for me as to whether a bug should be
back-ported to 1.2.x or not.  Given the lack of any "officially published"
guidelines, my own guidelines are as follows:

1) Enhancements don't get back-ported to either 1.4.x or 1.2.x.
2) Dissector bugs involving a lack of some decode can be back-ported to 1.4.x,
but not to 1.2.x, unless the bug was filed against 1.2.x.
3) Dissector bugs involving incorrect decode should be back-ported to both
1.4.x and 1.2.x.

I think #2 is a sort of gray area though.  A lack of some decode could be
considered an enhancement, so it shouldn't be back-ported, but it could also be
considered a deficiency, which it is, and so is a bug that would justify
back-porting.

I suspect that everyone has their own slightly different guidelines though. 
Maybe we should agree on some and post them somewhere?  It will make it a
little easier to decide when to or when not to back-port bug fixes.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.