From: David Sterba <dsterba@xxxxxxx> 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
