!aGqRytqbCECitOFhbt:nixos.org

Release Management

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

Load older messages


SenderMessageTime
27 Mar 2022
@janne.hess:helsinki-systems.deJanne Heßgreat, I didn't think of that :O17:30:41
@janne.hess:helsinki-systems.deJanne Heßmaintainers/subsystem-maintainers.txt maybe?17:30:57
@hexa:lossy.networkhexain gentoo joining a team is managed by existing team members and advertised on a wiki page17:31:11
@janne.hess:helsinki-systems.deJanne HeßI'll PR it and wait for a discussion to arise 🤷17:32:47
@vcunat:matrix.orgVladimír Čunát We have stuff like meta.maintainers = teams.gnome.members; 17:35:13
@vcunat:matrix.orgVladimír ČunátI mean... why txt?17:35:51
@janne.hess:helsinki-systems.deJanne HeßDo you think all people would be happy with being part of the team-list?17:36:37
@hexa:lossy.networkhexaoh yeah, reusing maintainer teams is a good idea17:38:54
@hexa:lossy.networkhexaI think this is a structured solution and a good middle ground17:39:25
@janne.hess:helsinki-systems.deJanne Heß

I agree with that for the language subsystems but what about these?

Nix/nix-cli ecosystem: @edolstra @grahamc @nbp @Profpatsch
Mobile: @samueldr
Nixos Modules / internals : @Infinisil @Ericson2314 @alyssais @roberth
Nixos tests: @tfc
Marketing: @garbas @tomberek
Docs: @ryantm @Mic92
Release: @tomberek @Mic92
17:39:37
@janne.hess:helsinki-systems.deJanne Heß(sorry if I pinged anyone…)17:39:53
@Ericson2314:matrix.orgJohn Ericsonlol you did17:49:59
@janne.hess:helsinki-systems.deJanne Heß:( Won't happen again, sorry17:50:11
@Ericson2314:matrix.orgJohn Ericsondon't worry about it :)17:56:17
@sandro:supersandro.deSandroThey could also be thrown into the maintainer teams. Than we can use them in derivation and so, too.22:44:31
@janne.hess:helsinki-systems.deJanne HeßI will try tomorrow if I find the time22:44:58
28 Mar 2022
@vlinkz:matrix.orgvlinkz joined the room.00:27:42
@janne.hess:helsinki-systems.deJanne HeßSecond attempt with the teams list and a script: https://github.com/NixOS/nixpkgs/pull/16597812:27:08
@janne.hess:helsinki-systems.deJanne Heß
In reply to @hexa:lossy.network
this feels like something that should be done once every release and a release manager wiki entry could be helpful to make sure it happens
What timespan should that be? Everything older than 1 year prior to the expected release date? (so June 2021 for 22.05)
18:20:14
@hexa:lossy.networkhexaI think it has two stages: 1) convert aliases to throws 2) remove throws18:20:57
@janne.hess:helsinki-systems.deJanne Heßah right… I didn't look at the mentioned PR18:21:56
@janne.hess:helsinki-systems.deJanne Heß * ah right… I didn't look at the mentioned PR too much18:21:58
@hexa:lossy.networkhexaa throw is the first user-facing action unless you've disabled aliases18:22:00
@janne.hess:helsinki-systems.deJanne HeßSo since this is the first release with that logic, we don't remove any aliases this time?18:22:18
@janne.hess:helsinki-systems.deJanne Heß

I have this for the wiki now:

- Remove old aliases that have been `throw`s for at least one release. There is
  a script in the nixpkgs tree to do that:
  `maintainers/scripts/remove-old-aliases.py --file
  ./pkgs/top-level/aliases.nix --year 2019 --month 6`
  The conversion to `throw`s is usually done in one big Pull Request so you can
  remove all aliases from the date prior to this Pull Request. [Example of the
  2022 throw conversion](https://github.com/NixOS/nixpkgs/pull/161146).
18:25:53
@lillecarl:matrix.orgLilleCarl joined the room.20:29:57
29 Mar 2022
@romildo:matrix.orgromildo joined the room.13:36:54
3 Apr 2022
@hexa:lossy.networkhexafwiw: i think the 22.05 milestone is a great tool to mark things for bulk closure after the release16:32:41
@janne.hess:helsinki-systems.deJanne Heß
In reply to @hexa:lossy.network
fwiw: i think the 22.05 milestone is a great tool to mark things for bulk closure after the release
are you alluding to the fact I closed the old milestones? 👀
16:33:45
@hexa:lossy.networkhexa uh, no. It was just about the discussion whether to use the project or the milestone 16:34:17

There are no newer messages yet.


Back to Room ListRoom Version: 6