From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: Next btrfs development cycle open - 4.21
Date: Mon, 17 Dec 2018 15:24:58 +0100 [thread overview]
Message-ID: <20181217142458.9486-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.
4.19 - current
4.20 - upcoming, urgent regression fixes only
4.21 - development closed, pull request in prep, fixes or regressions only
4.22 - development open, until 4.21-rc5 (at least)
(https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule)
Current status
--------------
The pull request for 4.21 will be sent on Wednesday 2018-12-19 because of the
end of year holiday timing and merge window start. This is a hard freeze for
patches that are not in for-next, small updates are pending.
My plan is to pull the 'enospc fixes' branch from Josef, as there are no
significant code changes planned. If this does not work, the fixes will go as
-rc updates.
The base of the pull request branch is misc-next, not yet forked as misc-4.21.
Hilights of 4.20 changes
------------------------
The more detailed description will be in the pull request, brief summary:
* swapfile support
* faster UUID change (incompatible change), does not need to rewrite all
metadata blocks, only stores the new one in the superblock
* balance prints the filter options to system log
* slightly faster filesystem balance, skips initial phase that tried to make
some space by shrink/grow
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
Note: git repository at repo.or.cz is discouraged from use
The devel repos should be identical regarding the main development branches
like misc-next or for-next-YYYYMMDD.
next reply other threads:[~2018-12-17 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 14:24 David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-09 16:40 Next btrfs development cycle open - 4.21 David Sterba
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=20181217142458.9486-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).