Wireshark mailing list archives
Re: Wireshark review to release
From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Sat, 21 Sep 2019 07:33:20 +0200
Hi, Like Roland stated, updates and enhancements are limited to the next version to be released, bug fixes go there too and are back ported. A very quick look at your committed changes seem to suggest to me these are bug fixes, the merger should have picked up on these. These would have to be revisited for consideration to back porting, IMHO. Jaap
On 20 Sep 2019, at 22:19, Roland Knall <rknall () gmail com> wrote: Hi Changes to master (which would happen the past months) will result in the code being in 3.2 (about to be released beginning next year). 3.0.x will just receive bugfix release kind regards Roland Am Fr., 20. Sept. 2019 um 21:56 Uhr schrieb Crawford, Anthony R <Anthony.R.Crawford () charter com <mailto:Anthony.R.Crawford () charter com>>: Good day all, I had the pleasure of providing some updates to a couple protocol dissectors last month. I was under the impression that cherry picked code into the master meant that the changes would be delivered in the next release but that does not appear to be the case. May you please help me understand how long it takes for code to be included in the stable release? Is there a “baking” period? Thanks, Anthony Crawford
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Wireshark review to release Crawford, Anthony R (Sep 20)
- Re: Wireshark review to release Roland Knall (Sep 20)
- Re: Wireshark review to release Jaap Keuter (Sep 20)
- Re: Wireshark review to release Roland Knall (Sep 20)