From: David Sterba <dsterba@xxxxxxx> Hi, a friendly reminder of the timetable and what's expected at this phase. Sorry for not sending it last time, I think it's useful so will try to keep the habit. 5.0 - current 5.1 - upcoming, urgent regression fixes only 5.2 - development closed, pull request in prep, fixes or regressions only 5.3 - development open, until 5.2-rc5 (at least) (https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#Development_schedule) Current status -------------- The branch misc-next is almost ready to be forked as misc-5.2 and sent as the first pull. There are 2 patchsets that have been in for-next and are eligible to be merged right away once some updates to changelogs arrive. There is one known bug causing hang of generic/500, it'll be resolved before misc-5.2 is branched. Hilights of 5.2 changes ------------------------ The more detailed description will be in the pull request, brief summary: - better read time and write checks to catch errors early and before writing data to disk (to catch potential memory corruption on data that get checksummed) - tree-checker updates to catch inconsistencies in various b-tree items ("inspired by fuzzing tools") - tracing events for b-tree locks - qgroups+metadata relocation: last speed up patch, there should be no overhead with and without qgroups when balancing metadata 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.2' 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
