In reply to @janne.hess:helsinki-systems.de
So Robert Hensing (roberth) grahamc (he/him): I wanted to finish up the discussion about the initial tag for the upcoming release. Graham said there might be tools that rely on the tag being named that way, do you think its enough to announce the upcoming change now and hope everybody relying on this fixes their scripts? I really understand Robert's motivation here and I think it would be a relevant improvement and make this more clear

[09:14:21] jon@nixos ~/projects/nixpkgs (release-21.11)
$ git describe
21.11-3617-g1f8e77dfaea

actually, for hydra this might not be too much of a concern:

  version = fileContents ../.version;
  versionSuffix =
    (if stableBranch then "." else "beta") + "${toString (nixpkgs.revCount - 291486)}.${nixpkgs.shortRev}";

And this gets updated as part of the release process

In reply to @janne.hess:helsinki-systems.de
I asked Graham to create the jobsets in advance and it doesn't appear to be an issue. The jobsets will not evaluate anyway because the branches are missing so this doesn't create additional load and gives us flexibility since we can just start evals from the hydra ui

In reply to @janne.hess:helsinki-systems.de
I asked Graham to create the jobsets in advance and it doesn't appear to be an issue. The jobsets will not evaluate anyway because the branches are missing so this doesn't create additional load and gives us flexibility since we can just start evals from the hydra ui

In reply to @vcunat:matrix.org
I also have the permissions, BTW (for future reference). Cloning jobsets and adjusting their parameters is quite easy.