Skip to content
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

New 0.7.x release? #9454

Closed
gdevenyi opened this issue Oct 11, 2019 · 8 comments
Closed

New 0.7.x release? #9454

gdevenyi opened this issue Oct 11, 2019 · 8 comments

Comments

@gdevenyi
Copy link
Contributor

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?

@GregorKopka
Copy link
Contributor

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.

@sempervictus
Copy link
Contributor

sempervictus commented Oct 13, 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.

@snajpa
Copy link
Contributor

snajpa commented Oct 14, 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.

@tonyhutter
Copy link
Contributor

@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.

@gdevenyi
Copy link
Contributor Author

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.

@GregorKopka
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@GregorKopka @snajpa @sempervictus @gdevenyi @tonyhutter and others