From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
DM-DEVEL ML <dm-devel@lists.linux.dev>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
Hannes Reinecke <hare@suse.com>,
Chris Hofstaedtler <zeha@debian.org>,
Christian Hesse <mail@eworm.de>,
Mitchell Dzurick <mitchell.dzurick@canonical.com>,
Steve Langasek <steve.langasek@ubuntu.com>
Subject: Re: Announcement: "stable" branches for multipath-tools
Date: Mon, 28 Apr 2025 11:12:08 -0400 [thread overview]
Message-ID: <aA-ayKBbfdplGtDb@redhat.com> (raw)
In-Reply-To: <8eee19603086bfa303af1a3d5446693aadf64d8b.camel@suse.com>
On Mon, Apr 28, 2025 at 03:56:30PM +0200, Martin Wilck wrote:
> On Sat, 2025-04-26 at 14:08 +0200, Xose Vazquez Perez wrote:
> > On 2/10/25 10:25 PM, Martin Wilck wrote:
> >
> > > the multipath-tools maintainers have decided to start providing
> > > stable
> > > branches that accumulate bug fix patches only. We currently provide
> > > two
> > > branches, stable-0.10.y [1] and stable-0.11.y [2].
> > >
> > > The stable branches are meant as a guideline for distribution
> > > maintainers to pick bug fixes without major regression risk. Only
> > > small
> > > patches that fix actual problems are eligible for inclusion in the
> > > stable trees.
> >
> > hwtable patches (
> > https://github.com/opensvc/multipath-tools/commits/master/libmultipath/hwtable.c
> > )
> > could be backported, as they are low risk.
>
> Yes, but they aren't actual, bug fixes, either, and they change default
> behavior, which I'd prefer to avoid in the stable branches.
>
> Ben, what's your take?
I think you're right. Even if we're just adding a new built-in config,
that could change how someone's multipath setup is configured, and while
the defaults are the recommeneded way to configure the device, it still
makes sense to not change them in what would otherwise be just a bugfix
branch, which is designed to safe to pull into a distribution at any
time.
On the other hand, if there are cases where an existing built-in config
is actually broken for a device, it would make sense to pull those fixes
into the stable branch.
-Ben
>
> Martin
prev parent reply other threads:[~2025-04-28 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 21:25 Announcement: "stable" branches for multipath-tools Martin Wilck
2025-04-26 12:08 ` Xose Vazquez Perez
2025-04-28 13:56 ` Martin Wilck
2025-04-28 15:12 ` Benjamin Marzinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aA-ayKBbfdplGtDb@redhat.com \
--to=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=hare@suse.com \
--cc=mail@eworm.de \
--cc=martin.wilck@suse.com \
--cc=mitchell.dzurick@canonical.com \
--cc=steve.langasek@ubuntu.com \
--cc=xose.vazquez@gmail.com \
--cc=zeha@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.