!aGqRytqbCECitOFhbt:nixos.org

Release Management

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

Load older messages


SenderMessageTime
1 Dec 2023
@tuxiqae:matrix.orgtuxiqae joined the room.07:05:56
@lennart:0520.chlennartwhat could be done about htat?08:36:31
@lennart:0520.chlennart * what could be done about that?08:36:34
@lennart:0520.chlennartwe should change these infos from 23.05 to 23.11 aswell https://nixos.org/manual/nixos/stable/#sec-upgrading08:38:08
@lennart:0520.chlennart
In reply to @lennart:0520.ch
we should change these infos from 23.05 to 23.11 aswell https://nixos.org/manual/nixos/stable/#sec-upgrading
doing a PR for that rn
08:39:17
@lennart:0520.chlennarteh, the Release commit was done correctly, changing these values https://github.com/NixOS/nixpkgs/commit/057f9aecfb71c4437d2b27d3323df7f93c010b7e08:45:25
@moritz.hedtke:matrix.orgmoritz.hedtke set their display name to Moritz Hedtke.11:08:06
@hexa:lossy.networkhexaisn't the manual published through the nixos-homepage repo?12:48:27
@figsoda:matrix.orgfigsodaIt seems that when I updated nixos-homepage the change isn't in nixos-23.11 yet14:12:27
@figsoda:matrix.orgfigsodamaybe I should have temporary switched it to release-23.1114:12:39
@figsoda:matrix.orgfigsoda*it's still not in nixos-23.11 yet14:13:28
@figsoda:matrix.orgfigsodahttps://github.com/NixOS/nixos-homepage/pull/117714:32:00
@julienmalka:matrix.org@julienmalka:matrix.org figsoda: apparently people are confused that 23.11 is still marked as beta 15:34:53
@julienmalka:matrix.org@julienmalka:matrix.org Is there a PR open to mark it as stable ? 15:35:04
@figsoda:matrix.orgfigsodaah ha I will go ahead and merge https://github.com/NixOS/nixos-search/pull/70715:35:26
@figsoda:matrix.orgfigsodathis should be fixed in a few minutes15:35:40
@julienmalka:matrix.org@julienmalka:matrix.orgHmmm15:35:45
@julienmalka:matrix.org@julienmalka:matrix.org Is that really the right change ? Is there not a json file somewhere to edit 15:36:00
@julienmalka:matrix.org@julienmalka:matrix.org Or it’s something else, I am just confused 15:36:53
@figsoda:matrix.orgfigsodathis essentially pulls in https://github.com/NixOS/nixos-org-configurations/pull/314 which marks 23.11 as stable. If you were referring to nixos search, this should be able to fix it15:37:03
@figsoda:matrix.orgfigsodait's live15:37:29
@figsoda:matrix.orgfigsodaimage.png
Download image.png
15:37:29
@julienmalka:matrix.org@julienmalka:matrix.orgAh thank you, I was thinking of this file, but I understand now why updating the flake lock is fixing the issue :)15:37:55
@lily:lily.flowersLily Foster
In reply to @julienmalka:matrix.org
Is that really the right change ? Is there not a json file somewhere to edit
i mean the flake lock is technically a json file that was edited (i am meaning this as a light-hearted joke, to be clear)
15:38:38
@julienmalka:matrix.org@julienmalka:matrix.org To be clear what I meant was 15:39:02
@julienmalka:matrix.org@julienmalka:matrix.orgIs there not a something something to edit ?15:39:11
@figsoda:matrix.orgfigsoda changed the room topic to "23.11 "Tapir" | https://nixos.github.io/release-wiki/Home.html" from "23.05 "Stoat" | https://nixos.github.io/release-wiki/Home.html".15:39:54
@kranzes:matrix.orgIlan Joselevich (Kranzes)Maybe update room's picture too?18:05:04
Room Avatar Renderer.19:17:09
2 Dec 2023
@julienmalka:matrix.org@julienmalka:matrix.org

Hello, I was discussing the other day with one of my advisors (Théo Zimmermann, who is a nixpkgs committer but not present here) about the difficulties we had for the release process this time, and he suggested a few improvements:

  1. During the branch-off, instead of doing changes to the release-branch, pushing and then also doing modifications to the master branch, he suggested we first open a PR to the master branch containing all the changes described in the Back on the master branch section of the wiki. This can be done before the branch-off and kept as a draft. At the branch-off, we first merge that PR, then we can work on the release branch in peace, knowing exactly on which commit basing this branch. This way we ditch all the problems of the type "the master branch advanced while we were working on the release branch". We also do not have to push on master.
  2. He suggested that instead of using the branch protections feature, we switch to "branch rules". Apparently, they are more expressive than the branch protections, and also appear publicly on the repo: https://github.com/NixOS/nixpkgs/branches --> by going to that page and clicking on the little shield, you get a list of all the rules applying to the branch
13:16:32

Show newer messages


Back to Room ListRoom Version: 6