Release Management | 343 Members | |
| 25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html | 93 Servers |
| Sender | Message | Time |
|---|---|---|
| 20 Nov 2023 | ||
In reply to @vcunat:matrix.orgoops, I removed the link for now, do you have a suggestion on an alternative? | 15:20:37 | |
| No, I don't know. | 15:23:27 | |
| Over the past months I've worked on My question: I'd like to add a release note for this towards the top of the highlights section, includes links to all of the above (reference docs, tutorial, Tweag blog and a shout-out to Antithesis). Do the release managers think this is okay or do you have any concerns? | 15:24:59 | |
| * Over the past months I've worked on My question: I'd like to add a release note for this towards the top of the highlights section, including links to all of the above (reference docs, tutorial, Tweag blog and a shout-out to Antithesis). Do the release managers think this is okay or do you have any concerns? | 15:25:24 | |
In reply to @infinisil:matrix.orgSounds fine with me, though I would leave the final say to the release editors, maybe open a PR and request a review from them when you're ready | 15:37:49 | |
In reply to @infinisil:matrix.orgI am not comfortable with a shout-out to Antithesis in the release notes | 15:40:20 | |
| And I'm not sure it's highlight worthy, it's Nixpkgs API, it's not totally relevant to NixOS IMHO, alas, we don't have good story for new Nixpkgs API, etc. | 15:41:04 | |
| But technically the place for "Nixpkgs notable changes" is its own section (we have internal changes and etc.) | 15:41:17 | |
For example, when I wrote the make-disk-image stuff and improved it: https://raw.githubusercontent.com/NixOS/nixpkgs/master/nixos/doc/manual/release-notes/rl-2305.section.md | 15:42:10 | |
| I just put it in some random place | 15:42:13 | |
I don't think the audience who is interested in lib.fileset will efficiently discover it via this way | 15:42:26 | |
| But I recognize there's a problem into how to highlight such changes | 15:42:45 | |
| I'd definitely highlight it in the Nix ecosystem newsletter for example | 15:43:05 | |
In reply to @raitobezarius:matrix.orgThere's no non-internal Nixpkgs highlights though | 15:43:12 | |
In reply to @infinisil:matrix.orgCorrect, we never had the need for it | 15:43:22 | |
| Because Nixpkgs API is an undefined object | 15:43:33 | |
| I like to call the API implicit :) | 15:44:03 | |
raitobezarius: What if I write a release notes section explicitly for lib changes? | 15:44:19 | |
| an explicitly undefined object, implicily defined, yes | 15:44:30 | |
In reply to @infinisil:matrix.orgThat works fine for me | 15:44:37 | |
| (but still not comfortable with a shout-out to company, I prefer to leave this in the introducing PR/eventual blog post and not put this information in the release notes) | 15:45:00 | |
(Ideally we'd have separate sections for pkgs, lib and nixos) | 15:45:21 | |
In reply to @raitobezarius:matrix.orgDoes a link to the blog post sound good though? | 15:45:44 | |
| Yep, that's fine | 15:45:49 | |
| Awesome thanks! | 15:46:16 | |
| Even if not in the release notes, I will give Antithesis all the shout-outs I can give. They deserve it, they enable me work on upstream Nix improvements all the time <3 | 15:51:45 | |
| That's completely fair, I just don't want to create difficult to handle precedents for this part of the documentation | 16:05:58 | |
| That does not say anything about Antithesis itself of course | 16:06:10 | |
| raitobezarius: Yeah understandable :) | 16:09:11 | |
| Though I think if there's any place for shout-outs, it should be the release notes. Maybe we could consider having a section for company shout-outs in the future. | 16:10:50 | |