Wireshark mailing list archives
Where do release branches come from?
From: chuck c <bubbasnmp () gmail com>
Date: Sun, 23 May 2021 16:43:32 -0500
There are currently three active branches: ( https://gitlab.com/wireshark/wireshark/-/branches/active) master, master-3.2 and release-3.4 My merge requests are to "master". If appropriate, it also gets backported ( https://www.wireshark.org/docs/wsdg_html/#ChSrcBackport) to master-3.2 and/or release-3.4. Soon (for some value of "soon") there will be a 3.6 branch. How do commits get from "master" (dev branch) to a stable branch? Will all of the commits in "master" make it to "release-3.6"? https://www.youtube.com/watch?v=SmHl7hKlVj4 "Speak as you might, to a young child. Or a golden retriever." thanks chuckc
___________________________________________________________________________ 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:
- Where do release branches come from? chuck c (May 23)
- Re: Where do release branches come from? Guy Harris (May 23)