!aGqRytqbCECitOFhbt:nixos.org

Release Management

340 Members
25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html93 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
1 May 2024
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.15:07:22
2 May 2024
@alejandrosame:matrix.org@alejandrosame:matrix.org
In reply to @jacg:matrix.org
Just in case I'm missing something important here, what exactly do you mean by 'rearrange the release notes'? Is there any larger-scale work to be done beyond things like making sure that the individual descriptions make sense and they adhere to a fairly consistent style?

In the previous release notes, I had as an editorial goal the rearrangement of sections. lennart (this account will be deactivated by 1st of may 2025) and I used a workflow that was not merged (context: https://github.com/NixOS/nixpkgs/pull/270967#issuecomment-2090332676), which turned into me sending a big update that moved pieces of text around, which complicated fixing the last minute release merge conflicts.

So, it's best to try to quickly merge drastic release notes changes ASAP to master. Although, my impression was also that towards the end of of the release cycle, the actual source of truth from the release notes perspective is the frozen branch, which then should be amended to master, not the other way around. At least, until we manage to get more granular control by generating the release notes.

12:17:22
@reckenrode:matrix.orgRandy Eckenrode I have a question about breaking changes. Is it breaking if a change does not affect eval or cause rebuilds, but it imposes a new restriction? Darwin dropped curl from the bootstrap, but it is possible for it to sneak back into the bootstrap. I have a change to make it throw, but that would prevent using fetchgit if you happen to be in the Darwin bootstrap. 14:25:09
@reckenrode:matrix.orgRandy EckenrodeIf it is, I can target 24.11 after staging opens back up to breaking changes.14:28:31
@wegank:matrix.orgWeijiaIt doesn't sound breaking to me (correct me if I'm wrong).14:35:20
@raitobezarius:matrix.orgraitobezarius
In reply to @reckenrode:matrix.org
I have a question about breaking changes. Is it breaking if a change does not affect eval or cause rebuilds, but it imposes a new restriction? Darwin dropped curl from the bootstrap, but it is possible for it to sneak back into the bootstrap. I have a change to make it throw, but that would prevent using fetchgit if you happen to be in the Darwin bootstrap.
can someone depend on that?
14:36:53
@raitobezarius:matrix.orgraitobezariusif so, it's a breaking change14:36:59
@raitobezarius:matrix.orgraitobezariusif not, it's not14:37:00
@raitobezarius:matrix.orgraitobezariusif it's a breaking change that's likely to be depended upon 0.5 folks, you can negotiate with RMs to find a compromise14:37:16
@reckenrode:matrix.orgRandy Eckenrode Sounds breaking because a package could switch to fetchgit or add curl as a dependency. 14:38:42
@reckenrode:matrix.orgRandy EckenrodeWhich happened with docutils. It’s fixed now, but other packages can do that.14:39:43
@reckenrode:matrix.orgRandy Eckenrode I can keep it a best effort exclusion for 24.05 and make it a hard block for 24.11. It’s not critical. More of a QoL improvement for curl updates. 14:40:56
@reckenrode:matrix.orgRandy Eckenrode * I can keep it a best effort exclusion for 24.05 and make it a hard block for 24.11. It’s not critical. More of a QoL improvement for curl updates, which have to go through staging anyway. 14:41:16
@raitobezarius:matrix.orgraitobezariusYeah, if it requires active cooperation from the package maintainer, this will be hard14:49:08

Show newer messages


Back to Room ListRoom Version: 6