Wireshark · Wireshark-dev: Re: [Wireshark-dev] Wireshark review to release

[Roland Knall <rknall@xxxxxxxxx>]

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@xxxxxxxxxxx>:

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

 

The contents of this e-mail message and
any attachments are intended solely for the
addressee(s) and may contain confidential
and/or legally privileged information. If you
are not the intended recipient of this message
or if this message has been addressed to you
in error, please immediately alert the sender
by reply e-mail and then delete this message
and any attachments. If you are not the
intended recipient, you are notified that
any use, dissemination, distribution, copying,
or storage of this message or any attachment
is strictly prohibited.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe