| 20 Nov 2023 |
 Randy Eckenrode | I think also Python 2. | 15:14:58 |
 raitobezarius | I think we could force our way through for Ruby 2.7 | 15:15:04 |
| Randy Eckenrode | * ~~I think also Python 2.~~ Nope, looks like it’s using the default OpenSSL. | 15:16:04 |
| raitobezarius | I don't think Python 2 or Ruby 2.7 are the problems here though | 15:16:04 |
| Randy Eckenrode | * ~I think also Python 2.~ Nope, looks like it’s using the default OpenSSL. | 15:16:10 |
| Randy Eckenrode | * <strike>I think also Python 2.</strike> Nope, looks like it’s using the default OpenSSL. | 15:16:19 |
| raitobezarius | We have too many dependencies still relying on OpenSSL 1.1 in nixpkgs | 15:16:27 |
| raitobezarius | like Sublime Text 4 | 15:16:43 |
| Randy Eckenrode | * I think also Python 2. Nope, looks like it’s using the default OpenSSL. | 15:16:44 |
 figsoda | * I'm thinking 7pm UTC | 15:19:57 |
| figsoda | In reply to @vcunat:matrix.org
The timezone link shows a bit confusing information that it's 8 PM in CEST. (It's 8 CET. CEST would be 9 but that zone isn't used now.) oops, I removed the link for now, do you have a suggestion on an alternative? | 15:20:37 |
 Vladimír Čunát | No, I don't know. | 15:23:27 |
 infinisil | Over the past months I've worked on lib.fileset a lot. It comes with reference docs, and I'm now als in the process of writing a tutorial. Furthermore, I might also be able to write a blog post on the Tweag website about it. And all of this work is graciously sponsored by Antithesis!
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 |
| infinisil | * Over the past months I've worked on lib.fileset a lot. It comes with reference docs, and I'm now als in the process of writing a tutorial. Furthermore, I might also be able to write a blog post on the Tweag website about it. And all of this work is graciously sponsored by Antithesis!
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 |
| figsoda | In reply to @infinisil:matrix.org
Over the past months I've worked on lib.fileset a lot. It comes with reference docs, and I'm now als in the process of writing a tutorial. Furthermore, I might also be able to write a blog post on the Tweag website about it. And all of this work is graciously sponsored by Antithesis!
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?
Sounds 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 |
| raitobezarius | In reply to @infinisil:matrix.org
Over the past months I've worked on lib.fileset a lot. It comes with reference docs, and I'm now als in the process of writing a tutorial. Furthermore, I might also be able to write a blog post on the Tweag website about it. And all of this work is graciously sponsored by Antithesis!
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?
I am not comfortable with a shout-out to Antithesis in the release notes | 15:40:20 |
| raitobezarius | 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 |
| raitobezarius | But technically the place for "Nixpkgs notable changes" is its own section (we have internal changes and etc.) | 15:41:17 |
| raitobezarius | 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 |
| raitobezarius | I just put it in some random place | 15:42:13 |
| raitobezarius | I don't think the audience who is interested in lib.fileset will efficiently discover it via this way | 15:42:26 |
| raitobezarius | But I recognize there's a problem into how to highlight such changes | 15:42:45 |
| raitobezarius | I'd definitely highlight it in the Nix ecosystem newsletter for example | 15:43:05 |
| infinisil | In reply to @raitobezarius:matrix.org
But technically the place for "Nixpkgs notable changes" is its own section (we have internal changes and etc.) There's no non-internal Nixpkgs highlights though | 15:43:12 |
| raitobezarius | In reply to @infinisil:matrix.org
There's no non-internal Nixpkgs highlights though Correct, we never had the need for it | 15:43:22 |
| raitobezarius | Because Nixpkgs API is an undefined object | 15:43:33 |
| infinisil | I like to call the API implicit :) | 15:44:03 |
| infinisil | raitobezarius: What if I write a release notes section explicitly for lib changes? | 15:44:19 |
| raitobezarius | an explicitly undefined object, implicily defined, yes | 15:44:30 |
| raitobezarius | In reply to @infinisil:matrix.org
raitobezarius: What if I write a release notes section explicitly for lib changes? That works fine for me | 15:44:37 |
