From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Subject: Next btrfs development cycle open - 4.16
Date: Tue, 24 Oct 2017 22:34:28 +0200 [thread overview]
Message-ID: <20171024203428.GV3521@twin.jikos.cz> (raw)
Hi,
a friendly reminder of the timetable and what's expected at this phase.
4.13 - current
4.14 - upcoming, urgent regression fixes only
4.15 - development closed, pull request in prep, fixes or regressions only
4.16 - development open, until 4.15-rc5
(https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule)
Besides the the usual cleanups and fixes, you can now start sending any
patches that could be more intrusive and would benefit from a longer
period of testing, or development revisions.
The base of the patches should be the last announced pull request, which
is going to be named 'for-4.15' 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.
k.org: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
devel1: http://repo.or.cz/linux-2.6/btrfs-unstable.git
devel2: https://github.com/kdave/btrfs-devel
d.
reply other threads:[~2017-10-24 20:36 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=20171024203428.GV3521@twin.jikos.cz \
--to=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).