!aGqRytqbCECitOFhbt:nixos.org

Release Management

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

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


SenderMessageTime
12 Oct 2023
@ajs124:ajs124.de@ajs124:ajs124.de changed their profile picture.21:50:35
14 Oct 2023
@lorenzleutgeb:matrix.org@lorenzleutgeb:matrix.org joined the room.13:41:22
15 Oct 2023
@kazimk:matrix.orgkazimk joined the room.17:35:52
16 Oct 2023
@figsoda:matrix.orgfigsodahttps://github.com/NixOS/nixos-artwork/issues/10416:45:58
@lennart:0520.chlennartAwesome will draft something the following days16:48:11
18 Oct 2023
@ghishadow:matrix.orgghishadow changed their profile picture.12:51:59
19 Oct 2023
@lennart:0520.chlennartfollowing up on that: https://github.com/NixOS/nixos-artwork/pull/10515:40:47
20 Oct 2023
@alejandrosame:matrix.org@alejandrosame:matrix.org

Hi all!

I've been working the last couple of days on a release notes generator after having merge conflicts and receiving feedback from contributors that wanted to have the file be split.

You can check the draft PR (https://github.com/NixOS/nixpkgs/pull/262296) and start giving feedback since I won't be refactoring the script and structure further.

I talked already with raitobezarius about this change and he also pointed me to ask here which approach would you like to take to move forward with the autogeneration of the release notes. The idea is that the we limit changes to the collected release notes file made by contributors. Some of the options are:

  • Having a bot autocommiting the release notes to the repo, so it is still rendered by github.
  • Limiting commiting to the main release notes file to only release managers and editors. The could from time to time generate the file and commit it to the relevant location.
  • Having a manual build output so people can check the rendered version locally. This would have to be done either way as part of the build task for the manual.

Please, share your ideas and comments :)

13:58:32
21 Oct 2023
@nki:m.nkagami.menki ⚡️ left the room.23:01:50
23 Oct 2023
@lennart:0520.chlennart wow this is super cool alejandrosame, I am a bit busy this week (due to having a night shift this week at work), but would give feedback the week after 06:16:27
@globin:toznenetl.chatglobin joined the room.09:50:49
@globin:toznenetl.chatglobin set a profile picture.14:27:46
25 Oct 2023
@federicodschonborn:matrix.org@federicodschonborn:matrix.org changed their profile picture.00:12:34
@fgaz:matrix.orgfgaz joined the room.07:40:17
27 Oct 2023
@federicodschonborn:matrix.org@federicodschonborn:matrix.org changed their profile picture.01:24:12
29 Oct 2023
@raitobezarius:matrix.orgraitobezariushttps://github.com/NixOS/nixpkgs/pull/25988411:54:23
@raitobezarius:matrix.orgraitobezariusmerged11:54:24
30 Oct 2023
@raitobezarius:matrix.orgraitobezariushttps://github.com/NixOS/nixpkgs/pull/26435813:56:00
@raitobezarius:matrix.orgraitobezariusdropping nodejs stuff13:56:03
@raitobezarius:matrix.orgraitobezariusI'm doing the ruby 3.0 drop PR too14:02:07
@raitobezarius:matrix.orgraitobezariusand I will drop probably some old LLVM stuff we can afford to drop14:02:16
@raitobezarius:matrix.orgraitobezariuswe don't have good solutions when the manual break because of removed services…14:09:19
@raitobezarius:matrix.orgraitobezariusdo we?14:09:22
@raitobezarius:matrix.orgraitobezariushttps://github.com/NixOS/nixpkgs/pull/26436114:13:11
@vcunat:matrix.orgVladimír ČunátOld clang is easier to drop than old gcc? IIRC we didn't get far there.14:14:03

Show newer messages


Back to Room ListRoom Version: 6