Wireshark-bugs: [Wireshark-bugs] [Bug 12268] Stack exhaustion in proto_tree_traverse_XXX_order
Date: Tue, 19 Apr 2016 21:31:20 +0000

changed bug 12268


What Removed Added
Severity Blocker Critical

Comment # 8 on bug 12268 from
(In reply to Christopher Maynard from comment #7)
> This bug was set to a Blocker severity.  Should it be marked as Critical,
> rather than Blocker or is Wireshark using Blocker for bugs that block the
> next release?  But then if that's the case, shouldn't bug 10456 and bug
> 10606, both opened in 2014, also be fixed before the next release?
> 
> https://www.mediawiki.org/wiki/Bugzilla/Fields#Severity

Critical is arguably more correct. I'm not sure why bugs 10456 & 10606 are
marked Blocker but IMHO they should be Major or lower.


You are receiving this mail because:
  • You are watching all bug changes.