From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: Next btrfs development cycle open - 5.5
Date: Mon, 9 Sep 2019 17:07:57 +0200 [thread overview]
Message-ID: <20190909150757.5713-1-dsterba@suse.com> (raw)
From: David Sterba <dsterba@suse.cz>
Hi,
a friendly reminder of the timetable and what's expected at this phase.
5.2 - current
5.3 - upcoming, urgent regression fixes only
5.4 - development closed, pull request in prep, fixes or regressions only
5.5 - development open, until 5.4-rc5 (at least)
(https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule)
Current status
--------------
Branch misc-5.4 has been forked off misc-next (based on 5.3-rc8) and contains
the first pull request changes. I'm going to send an early pull request
before the merge window starts, due to travelling.
There are some fstest failures or things worth closer look, now is the time.
Hilights of 5.4 changes
------------------------
The space handling has been reworked, getting rid of some corner case behaviour
and improving the logic to address it from higher level (that's my interpretation).
Tree checker has learned some new tricks (inode item checks).
Again there are many cleanups and refactoring.
Pending features
----------------
There are several patchsets implementing new features. Please note that the
reviewer bandwidth stays mostly constant, not much chance to make things
faster.
The patchsets reworking the core things get a slight preference over features
as they can be verified by functional testing and do not impact user
interfaces.
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
Usual points
------------
* the current patch queue (as is in misc-next) looks stable, so no big
changes are going to be applied at this time. The usual exceptions are
bugfixes or obvious cleanups.
* the base of the patches should be the last announced pull request,
which is going to be named 'for-5.4' in my k.org tree. Reviewed
patches will be collected in a branch that's usually named 'misc-next'
in my devel git repos and is part of the for-next at k.org git repo.
* merging of new patches to misc-next will be slow during the
merge window
* review other developer patches, test them, find bugs before they are in a
released kernel
reply other threads:[~2019-09-09 15:07 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=20190909150757.5713-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;
as well as URLs for NNTP newsgroup(s).