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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add information on release cycle and backports #9004

Merged
merged 3 commits into from
Sep 29, 2023
Merged

add information on release cycle and backports #9004

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
954890a
add information on release cycle and backports
fricklerhandwerk Sep 21, 2023
1b560ea
more detail on backports
fricklerhandwerk Sep 21, 2023
a757749
reword for readability
fricklerhandwerk Sep 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions doc/manual/src/release-notes/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1,11 @@
# Nix Release Notes

Nix has a release cycle of roughly 6 weeks.
Notable changes and additions are announced in the release notes for each version.

Bugfixes can be backported on request to previous Nix releases.
We typically backport only as far back as the Nix version used in the latest NixOS release, which is announced in the [NixOS release notes](https://nixos.org/manual/nixos/stable/release-notes.html#ch-release-notes).

Backports never skip releases (if a feature is backported to `x.y`, it must also be available in `x.(y+1)`;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this is actually a policy we're currently following. Backports are pretty much by request.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not, but @roberth would like to make it such. Declaring it here may be a good start.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's nice in theory, but also potentially a lot of extra work, which might make us more reluctant to backport bug fixes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's really important. If backports skip releases, we are introducing breaking changes.

This ensures that upgrading from an older version with backports is still safe and no backported functionality will go missing.