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.
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
> however users will get access via UI in the next update.
Update after next-- we'll be doing a short release for segwit support right after 0.15.
Feature freeze for 0.15 (next release) was scheduled on July 16th ( https://github.com/bitcoin/bitcoin/issues/9961 ), segwit lock-in wasn't until aug 9th. We'd shortcut the process for a serious emergency, but not for something short of one.
I'm sorry, I have to be a bit negative on this one.
- No release notes! (as of 1 hour after story posted)
- Network stack re-written. They kinda flubbed network the first time, creating assymetric network and double nat conditions. And within one release, there's a complete re-write with a new networking model? This is going to take a lot of proving to ensure that it's actually going to work for production systems. In the meantime, we at least are going to continue using --net=host for our containers.
- Another storage format. Can we simply get one that's stable, please?
- Volume re-write. Ditto networking.
- [EDIT2] Disregard previous edit entirely - now you're simply disallowed from using devicemapper entirely, if you're using the officially compiled Docker binary for Ubuntu 14.04 and 15.04? [4] What the actual fuck is going on here Docker? AUFS has significant performance issues (not even mentioning the deprecated part), OverlayFS requires a release candidate Linux kernel, ZFS as a storage backend is brand spanking new, and btrfs is as stable as a three legged chair. By the way, this affects CentOS and RHEL.
[EDIT]: 1.7 appears to have fixed the superficial problem - using the wrong devicemapper drivers. Would still prefer to have a proper package.
[ORIGINAL] The whole "devicemapper on Ubuntu 14.4" [1] snafu appears to still in full force [2]. Why can't they offer properly compiled OS packages? They're distributing them as OS/Architecture specific packages...
Note - AUFS is not a real choice for (at least) node applications, we ran into an issue back on 1.6 where there was a low level mutex limiting concurrency on AUFS which did not appear on devicemapper. [3]
Not yet, I've got one more milestone to hit before I make it public, and I'm working on some other things before I tackle that.
Release milestones are SMP, networking, amd64. SMP works! Networking works for realtek gigE and virtio-net! amd64 hasn't been started (runs x86-32 bit) and will be a big task and should touch a lot of the kernel and clean up.
But, I wasn't trying to hijack this thread. Email me.
Huh, I’m not really tracking UNIX releases anymore but I thought that 14.0 has been out for a while. My pfSense router has been claiming to run on 14.0 since may 2023:
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.
reply