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

[19.09] linux: drop non-LTS versioned kernel attributes #70202

Merged
merged 1 commit into from Oct 7, 2019

Conversation

alyssais
Copy link
Member

@alyssais alyssais commented Oct 1, 2019

Quoting the release manual:

Remove attributes that we know we will not be able to support,
especially if there is a stable alternative. E.g. Check that our Linux
kernels' projected end-of-life are after our release projected
end-of-life

@alyssais alyssais added this to the 19.09 milestone Oct 1, 2019
@samueldr
Copy link
Member

samueldr commented Oct 7, 2019

@NeQuissimus We've discussed this over on IRC, and there's only one question left to answer, and only you can answer it.

Would dropping the named attributes for non-LTS kernel version cause issues with backporting from master to stable?

We figured that it may cause the kernel introduction cherry-pick to conflict in all-packages.nix, nothing else though.

This PR (and the release docs paragraph) about dropping versioned attribute names from stable releases currently hinges on that question alone.

Thanks!

@NeQuissimus
Copy link
Member

No problem, the individual versions should still cherry-pick just fine (i.e. linux-5.3.nix).
I am okay with some additional work when going between master and stable.

Quoting the release manual:

> Remove attributes that we know we will not be able to support,
> especially if there is a stable alternative. E.g. Check that our Linux
> kernels' projected end-of-life are after our release projected
> end-of-life
@alyssais alyssais merged commit 5b93ae1 into NixOS:release-19.09 Oct 7, 2019
@alyssais alyssais deleted the drop-kernels branch October 7, 2019 20:17
@grahamc
Copy link
Member

grahamc commented Oct 7, 2019

🎉

@d-goldin
Copy link
Contributor

Maybe it's worth including this and a suggested "fix" in the release notes.

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

Successfully merging this pull request may close these issues.

None yet

6 participants