Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-29 Thread Guy Harris
On Jun 28, 2019, at 7:11 AM, Maynard, Chris wrote: > You can find the download link by navigating from https://www.wireshark.org/ > -> Download -> More downloads and documentation can be found on the downloads > page -> Live on the Bleeding Edge: You can download source code packages and >

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-28 Thread Jaap Keuter
Hi Jason, Indeed, not so easy to find. The roadmap[1] states the intention to have a decent snapshot of the current developments in 3.1 posted as development build on the front page at about July 18th. Thanks, Jaap [1] https://wiki.wireshark.org/Development/Roadmap

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-28 Thread Graham Bloice
June 28, 2019 9:36 AM > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev] Question about dissector "enhancement" / > bug > > > > >> See the automated build section, dev builds for Windows and OSX: > https://www.wireshark.org/download

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-28 Thread Maynard, Chris
boun...@wireshark.org] On Behalf Of Jason Cohen Sent: Friday, June 28, 2019 9:36 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Question about dissector "enhancement" / bug >> See the automated build section, dev builds for Windows and OSX: >> h

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-28 Thread Jason Cohen
>> See the automated build section, dev builds for Windows and OSX: https://www.wireshark.org/download/automated/. >> These builds are produced when a merge is made to the appropriate master branch. The point wasn't for me. ;) it was for the thousands+ of users that depend on wireshark to

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-28 Thread Graham Bloice
On Fri, 28 Jun 2019 at 13:49, Jason Cohen wrote: > All fair points. I won't push any further. > > >> My pulled from the air guess is the set of users that need these > incremental dissector\protocol changes is much smaller than the entire set > of users, and their needs are served by the

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-28 Thread Jason Cohen
All fair points. I won't push any further. >> My pulled from the air guess is the set of users that need these incremental dissector\protocol changes is much smaller than the entire set of users, and their needs are served by the development branch. Yes, the set of users is much smaller than

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-28 Thread Graham Bloice
On Fri, 28 Jun 2019 at 06:50, Pascal Quantin wrote: > Hi, > > Le ven. 28 juin 2019 à 06:06, Anders Broman a > écrit : > >> >> >> Den fre 28 juni 2019 00:44Jason Cohen skrev: >> >>> The question about about weather or not adding dissection of additional >>> information in a dissector is an

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-27 Thread Pascal Quantin
Hi, Le ven. 28 juin 2019 à 06:06, Anders Broman a écrit : > > > Den fre 28 juni 2019 00:44Jason Cohen skrev: > >> The question about about weather or not adding dissection of additional >> information in a dissector is an enhancement or a bug; I think this is kind >> of a grey area. If a

Re: [Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-27 Thread Anders Broman
Den fre 28 juni 2019 00:44Jason Cohen skrev: > The question about about weather or not adding dissection of additional > information in a dissector is an enhancement or a bug; I think this is kind > of a grey area. If a dissector doesn't completely dissect a header, would > a patch that

[Wireshark-dev] Question about dissector "enhancement" / bug

2019-06-27 Thread Jason Cohen
The question about about weather or not adding dissection of additional information in a dissector is an enhancement or a bug; I think this is kind of a grey area. If a dissector doesn't completely dissect a header, would a patch that completes it be considered fixing it? Does it switch between