There is an update to the rtps protocol that I need in the 3.7 release. My organization is kind of sketch on using dev releases, so I was wondering when 3.7 was expected to have a release version rather than a development version? I've been searching the site, but I can't find it.
Thanks
You're looking for the next even Major (4.0) or Minor (3.8) release - ReleaseNumbers
The Roadmap lists:
4.0.0rc1 August 3, 2022 First release candidate for Wireshark 4.0.0
This is a SWAG which might get tweaked during Sharkfest ’22 US next week or due to things that pop up in the development/release process.
I finally found the answer to my own question, in part. Release information can be found at this page: https://wiki.wireshark.org/Developmen...
The problem is it does not mention 3.7, which is where the change I need resides... is 3.7 just going to be rolled into the 4.0 stuff? Any info as to when this might be provided in a stable release would be appreciated.
A few more details: The rtps protocol dissector has a bug fix so that union information can be seen within the dissection. This fix is required for my particular project. Since my org does not like deploying dev releases of software, I need a stable release if at all possible. I'm not even sure if this type of bug would qualify as a "bug fix" under the guidelines, so while I know how to backport it, I'm not sure if I should attempt it.
Any info appreciated.
Sounds like RTPS: ixed dissection of unions in user data. should be pulled into the 3.6 branch ?
Not that it fixes your issues, but Wireshark is a diagnostic tool, does it really matter if you're running a dev or release build? How does the Wireshark release status affect your RTPS production software?
It's not the type of tool, but the fact that it would be deployed in a controlled environment. Security guys get squeamish over dev software because it has not completed its full review process.
Any idea on how to request this patch be pulled into the 3.6 branch in the appropriate manner?
Normally an "issue" is raised and then merge requests for various branches are raised from that. In this case no issue was raised (that I can see), just the direct MR so you'll have to add a note to the MR.
Comments