From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: Next btrfs development cycle - 5.10
Date: Wed, 29 Jul 2020 18:26:27 +0200 [thread overview]
Message-ID: <20200729162627.30743-1-dsterba@suse.com> (raw)
From: David Sterba <dsterba@suse.cz>
Hi,
a belated friendly reminder of the timetable and what's expected at this phase.
5.7 - current
5.8 - upcoming, urgent regression fixes only
5.9 - development closed, pull request in prep, fixes or regressions only
5.10 - development open, until 5.9-rc5 (at least)
(https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule)
Current status
--------------
The pull request branch has been forked off misc-next, it's named misc-5.9.
Merge window most likely opens on Monday and I'm going to send early pull
request on Friday.
Hilights:
- mount option updates
- performance improvements (parallel fsync)
- balance interruptible by ctrl-c
- more information exported in sysfs (qgroups, bdi)
Lots of cleanups and fixes otherwise.
Merge outlook
-------------
First look back, 5.9 queue does not have any big core changes, rather lots of
cleanups, small enhancements and stabilization. The mirror balancing or chunk
dump ioctl have not made much progress, so that's for another cycle. I should
rather not make any predictions.
From now on only selected fixes will be merged to 5.9 queue. In 5.10 we'll do
the reworked ticket reservations for data, the reviews came too close to the
freeze. The dio-iomap will probably be merged too as the wider iomap updates
are about to be merged. Otherwise, there are several RFC patches or older
patchsets, we'll see what will be in mergeable state.
Git development repos
---------------------
k.org: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
devel1: https://gitlab.com/kdave/btrfs-devel
devel2: https://github.com/kdave/btrfs-devel
reply other threads:[~2020-07-29 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200729162627.30743-1-dsterba@suse.com \
--to=dsterba@suse.com \
--cc=dsterba@suse.cz \
--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