Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.3
Date: Thu, 27 Apr 2023 15:10:44 +0200	[thread overview]
Message-ID: <20230427131044.6804-1-dsterba@suse.com> (raw)

Hi,

btrfs-progs version 6.3 have been released.

There are some fixes and tweaks, the experimental status of block-group-tree
has been removed, namely the conversion but please still use it with care.

Otherwise there's nothing interesting from users' POV, more documentation is
being moved from archived wiki, updated tests.

The CI on github has been extended to cover devel and pre-release branches,
further enhancements are planned to do e.g. quick build tests for pull requests
or use self-hosted runners for heavier tests that may need to run against a
recent kernel. (https://github.com/kdave/btrfs-progs/actions)

Release process now uses more of the github features, so besides the tag itself
there's also a release with changelog (https://github.com/kdave/btrfs-progs/releases).
This allows to add "artifacts" i.e. other files besides the sources.

There are now static binaries published along with the release. They're built
inside the CI workflow "Static binaries" (also available there for download).
The upload is still done from an intermediate host so if you don't trust github
CI or me copying the files as-is, please build and use your own.

Please let me know if you have suggestions for improvements or if you find
problems with the CI/release things. It's new to me and I'm sure the are
already best practices to follow.

Changelog:
   * mkfs: option -R deprecated, options unified in -O (-R still works)
   * mkfs: fix potential race with udev leading to EBUSY due to repeatedly
     opened file descriptors
   * block-group-tree is out of experimental mode
      * available as 'mkfs.btrfs -O block-group-tree'
      * btrfstune can do in-place conversion to/from (use with care)
   * balance: fix recognizing old and new syntax
   * subvol snapshot: specific error if a failure is caused by an active swapfile
   * tree-stats: rephrase warning when run on a mounted filesystem
   * completion: 'filesystem du' also completes files
   * check: fix docs, help text and warning that --force + --repair works on a
     mounted filesystem
   * build: fix static build when static libudev is available
   * documentation:
      * more updates from wiki, developer docs, changelogs
      * reformatting
      * updates and fixes
   * other:
      * test updates and fixes
      * CI cleanups and old files removed
      * integration with Github actions

Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git

             reply	other threads:[~2023-04-27 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 13:10 David Sterba [this message]
2023-04-27 19:44 ` Btrfs progs release 6.3 Neal Gompa
2023-04-27 20:29   ` David Sterba

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=20230427131044.6804-1-dsterba@suse.com \
    --to=dsterba@suse.com \
    --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