From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 4.16.1
Date: Wed, 25 Apr 2018 06:31:20 +0000 (UTC) [thread overview]
Message-ID: <pan$3f697$9cfd5cd2$6e9f2dc3$73937e71@cox.net> (raw)
In-Reply-To: 20180424115857.25174-1-dsterba@suse.com
David Sterba posted on Tue, 24 Apr 2018 13:58:57 +0200 as excerpted:
> btrfs-progs version 4.16.1 have been released. This is a bugfix
> release.
>
> Changes:
>
> * remove obsolete tools: btrfs-debug-tree, btrfs-zero-log,
> btrfs-show-super, btrfs-calc-size
Cue the admin-side gripes about developer definitions of micro-upgrade
explicit "bugfix release" that allow disappearance of "obsolete tools".
Arguably such removals can be expected in a "feature release", but
shouldn't surprise unsuspecting admins doing a micro-version upgrade
that's specifically billed as a "bugfix release".
(Further support for btrfs being "still stabilizing, not yet fully stable
and mature." But development mode habits need to end /sometime/, if
stability is indeed a goal.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2018-04-25 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 11:58 Btrfs progs release 4.16.1 David Sterba
2018-04-25 6:31 ` Duncan [this message]
2018-04-25 11:02 ` David Sterba
2018-04-25 11:22 ` Austin S. Hemmelgarn
2018-04-25 11:29 ` Christoph Anton Mitterer
2018-04-25 11:49 ` Austin S. Hemmelgarn
2018-04-25 17:56 ` Duncan
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='pan$3f697$9cfd5cd2$6e9f2dc3$73937e71@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox