[tcpdump-workers] how many stable branches to have
mcr at sandelman.ca
Thu May 21 14:16:32 EDT 2015
There was a discussion about what branches to possibly backport fixes to.
Guy has related:
Guy Harris <guy at alum.mit.edu> wrote:
> Wireshark has:
> * the current development branch (master, trunk, whatever);
> * the current stable branch (currently 1.12);
> * the current "old stable" branch (currently 1.10);
> Security fixes are backported to the stable and "old stable" branches
> if they apply (or committed to those branches if they don't exist in
> the trunk), as are some other bug fixes.
I don't think that we need to have both stable and old-stable.
People asked for more regular releases awhile ago, and I said that I'd get
two releases out a year, possibly three, and that they would most likely be
aligned with IETF Spring and Fall meetings.
(IETF meetings have gotten really busy/exhausting for me of late, so
sometimes things have slipped)
> There are also lts-1.12.1, lts-1.2.11, and lts-1.8.2 branches that were
> created by Balint Reczey, the maintainer of the Wireshark Debian
> package, for the benefit of Debian; he backports fixes to those
> branches for incorporation into older Debian releases. Presumably
> other distributions'/*BSDs/etc. maintainers could create their own lts-
> branches if they want.
> We might want either to pick a set of "long-term support" branches to
> which we'll backport security fixes and at least some other fixes, or
> offer a similar option to maintainers to create their own lts-
I have no problem with having lts- branches created for distros, and I'd
rather do that than have "old stable". I'd rather call them something like:
so that we'd know both where it is going, and also when we can abandon
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr at sandelman.ca http://www.sandelman.ca/ | ruby on rails [
More information about the tcpdump-workers