Next btrfs development cycle open - 4.21

Next btrfs development cycle open - 4.21

[David Sterba]

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 btrfs development cycle open - 4.21

[David Sterba]

From: David Sterba <dsterba@suse.cz>

Hi,

a friendly reminder of the timetable and what's expected at this phase.

4.18 - current
4.19 - upcoming, urgent regression fixes only
4.20 - development closed, pull request in prep, fixes or regressions only
4.21 - development open, until 4.20-rc5 (at least)

(https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule)

Whether the next version is going to be 4.20 or 5.0 I don't know, I'll use the
4.x for references. There will be 4.19-rc8 milestone, probably the last one
before the final release.


Current status
--------------

The branch misc-4.20 contains patches that will be sent in the first 4.20
batch.  There are about 90, fewer than in previous cycles.

There might be 2nd pull sent during the merge window, the reviews are going
slow but there are still patches/fixes that I'd like to get merged.


Hilights of 4.20 changes
------------------------

The more detailed description will be in the pull request, brief summary:

* (performance) relocation with qgroups on -- skip unnecessary qgroup
  accounting work during merging b-trees after relocation, claimed improvement
  is 20-40%+ (run time) but highly depends on the extent layout

* (performance) b-tree path traversal and locking improvements -- no more
  switching between blocking and spinning mode, sample measurements show
  noticeable improvements in latency and run time

* (performance) rb-tree caching -- repeated tree traversal does not need to
  spend time chasing pointers up to the first node


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.


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-4.20' 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, also because there's a btrfs-progs release scheduled

* everybody is encouraged to review and test other's patches