New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zfsUnstable: 2.0.0-rc2 -> 2.0.0-rc3 #99361
Conversation
Result of 18 packages built:
|
@ofborg test zfs.unstable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
diff LGTM
tests pass
Should this be backported (maybe after the 20.09 release)? |
generally I would say no, but it's explicit about itself being unstable. Seeing as most of the changes are bugfixes, I would say yes |
Well, rc2 is part of 20.09 as the unstable version, so that decision seems to have been made already. ^^ |
I think that zfsUnstable inside the release branch exists because we also add new kernels to the release branch, and zfs (stable) was not that good in supporting new kernels, so people saw a need to use zfs unstable. That has changed, as the stable zfs branch is pretty good in support new kernels. But yes, -rc3 should be backported, given the precedent with 2.0.0-rc1/rc2. The real question is what we do when 2.0.0 stable gets released :). Do we go back and make zfsUnstable track the zfs master branch? |
@clefru In the past, |
Motivation for this change
More bugfixes: https://github.com/openzfs/zfs/releases/tag/zfs-2.0.0-rc3
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)