Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
* Next btrfs development cycle open - 5.5
@ 2019-09-09 15:07 David Sterba
  0 siblings, 0 replies; only message in thread
From: David Sterba @ 2019-09-09 15:07 UTC (permalink / raw)
  To: linux-btrfs; +Cc: David Sterba

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-09 15:07 Next btrfs development cycle open - 5.5 David Sterba

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org linux-btrfs@archiver.kernel.org
	public-inbox-index linux-btrfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox