If you follow one for nixpkgs, it means that the infrastructure has at least attempted all possible builds. If you're starting to build something, it's likely broken. However, that's usually not the case. https://hydra.nixos.org/jobset/nixos/release-21.05
The latest version of something failing to build. Like when the Tor project removes a Tor Browser package from its servers and `tor-browser-bin` hasn't yet been updated in nixpkgs.
That is the 10.0 release announcement. The directory linked here is not-yet-released 10.1.
As always, until the release announcement comes out, the release is not done. Until that time, there's always a possibility the release builds will need to be rebuilt for some reason.
Releases is not the proper word here. It should be 'US DoD starts using 11.0.0.0/8'. Nowhere in that thread does it say the subnet is being released back into the generally available pool, just that it's started to be routed.
> At this point we have a set of images that we consider release grade, pending final testing, we will move to release these unless a major blocker is reported.
I don't love that a post from July talked about stabilizing and releasing 2.4 "in the next few weeks", and now it's September with still no release. OTOH, the list of milestone issues is pretty short:
It seems that all of their recent releases are either testing releases ([1] [2]), or bug fix releases relative to testing releases ([3]), or bug fix releases relative to bug fix releases relative to testing releases ([4]).
TFA is a stable channel announcement. Everything in it has been available for a while now, but under the mainline channel. Like a new release of Ubuntu getting Linux 4.4 while Arch and Gentoo are on 4.5 already.
Those may not be final, mirrors resync release files all up to the release day.
They are probably as valid as all snapshots around release day, as long as the signify keys check out fine, but no guarantees for that set to be 100% identical with what ends up being the actual release.
Specifically, a supported release is one which will receive patch updates (e.g. for security flaws or other issues).
If you do not use a "supported version", you'll have to scramble to update or backport patches yourself if you're hit by a serious issue that is fixed upstream.
Released in nixos-20.09 on Mar 16 16:31:31 UTC (four days later)
Again, four days is not great for a Chrome zero-day. NixOS doesn't have a professional security team, and if you need that assurance, maybe you can't use it. But please don't exaggerate and muddy the facts.
Most of the delay is due to hydra having to build everything that came in ahead of that change on the master branch, and sometimes the master branch is just broken.... I wish there was a fast-track process that could bump urgent security changes ahead of other ones, but it seems like it could complicate things a lot.
Of course, as I said above, it's relatively easy for you to update your local install without waiting for all that, if you're aware of the release and its severity.
s/Most/All/. I've never heard of a release candidate meaning anything else, it's something you'll release as-is with a non-rc version unless critical bugs emerge. This is a beta, not a RC.
Still a little odd for a release announcement. It feels disingenuous to only afterwards make the fine-grained distinction that yes the libraries are technically v1, but the tooling is still in preview.
Kinda like announcing your new line of cars is ready for purchase today! Except that down in the fine print you might find out that the engine is ready to go, but the steering wheel, headlights, dashboard, and pedals are all still in development and so it's justifiable that they're broken.
If you follow one for nixpkgs, it means that the infrastructure has at least attempted all possible builds. If you're starting to build something, it's likely broken. However, that's usually not the case. https://hydra.nixos.org/jobset/nixos/release-21.05
reply