We've had two releases of 0.8.x since 0.7.13 and there's a number of important bugs that could justify backporting.
What's the current status of another 0.7.x release?
gdevenyi
All 6 comments
A stable version that gets only bugfixes (and no new features that have a fair chance to bring new issues) would be a nice thing to have for production.
GregorKopka
on 13 Oct 2019
There is no stable, there is only Zuul. Stable comes @ 1.0 - every release so far has introduced new functionality or bug fixes, broken things that worked previously either completely or under edge-case conditions, and improved performance in one set of tests while degrading it in another. Try running a high performance SCST block export from a ZVOL these days - used to work (without throwing kernel stack traces) when ZVOLs had the entire linux block layer in them, but that's been broken since ~0.6.4 or so.
Distributions can make their own stable backports - doesn't Ubuntu (Canonical i guess) pay someone to do that? Or users can learn how to backport commits themselves so they can figure out just how interdependent the work on master is with other changes slated for contemporaneous commit. Getting the range tree work into 0.8.2 for instance takes some time with git and a lot of test builds, i wouldn't want to try and do that for a 7.x branch.
sempervictus
on 13 Oct 2019
I'd be for having new releases in both 0.7.x 0.8.x branches for the foreseeable future, but I'm in no position to vote, as we're running wild versions too (master at various points of time) and I think the next possible branch I could help maintaining would be whatever comes after 0.8.x.
Then I'd be strictly for fixing compile errors on newer kernels + stability fixes, no performance nor patches of any other sort than strictly of this nature - for the stable branch to run on new kernels + keep fixing crashes/lockups/leaks/documentation errors.
snajpa
on 14 Oct 2019
@gdevenyi there are no plans for a future 0.7.x release. It's all going to 0.8.x. The branches have diverged so much that it would be a major headache to backport anything to 0.7.x anyway.
tonyhutter
on 17 Oct 2019
RIP 0.7.14: https://github.com/zfsonlinux/zfs/projects/22
I guess I'll have to decide on what to do about my 0.6.5.11 file servers.
gdevenyi
on 17 Oct 2019
I guess I'll have to decide on what to do about my 0.6.5.11 file servers.
I guess the same as I do with mine: keep them as-is till the day there hopefully will be a zfs on linux release that dosn't contain showstopper issues.
GregorKopka
on 19 Oct 2019
Related issues
bwatkinson
路
50Comments
wrouesnel
路
57Comments
tycho
路
67Comments
user318
路
51Comments
cytrinox
路
66Comments
Most helpful comment
There is no stable, there is only Zuul. Stable comes @ 1.0 - every release so far has introduced new functionality or bug fixes, broken things that worked previously either completely or under edge-case conditions, and improved performance in one set of tests while degrading it in another. Try running a high performance SCST block export from a ZVOL these days - used to work (without throwing kernel stack traces) when ZVOLs had the entire linux block layer in them, but that's been broken since ~0.6.4 or so.
Distributions can make their own stable backports - doesn't Ubuntu (Canonical i guess) pay someone to do that? Or users can learn how to backport commits themselves so they can figure out just how interdependent the work on master is with other changes slated for contemporaneous commit. Getting the range tree work into 0.8.2 for instance takes some time with git and a lot of test builds, i wouldn't want to try and do that for a 7.x branch.