Upgraded f23 x86_64 with no issues and rebooted with no issues.

Tun device no longer created at boot. https://bugzilla.redhat.com/show_bug.cgi?id=1330212

New package, so nothing can break...

Installed from scratch on CentOS-6.7 x86_64. Comes up out of the box with zero config (another cjdns node was alread on the LAN).

Yum pulled in libuv-0.10.34 as a dependency. The /usr/sbin/cjdroute does not use libuv dynamically, but embeds 0.11.4. I don't know where the dependency came from - I just double checked the SPEC. Ultimately, the goal is to use the system libuv, so I don't think this is a problem.

Updated nacl with existing cjdns (local) build on centOS-7 with no problems. Reinstalled cjdns from epel-testing and that works too.

Haven't gotten the 24-alpha ISO yet, to actually test, but might as well make it easy to install and test once 24 is out.

Updated i686 system with cjdns using (locally built) libnacl.so.0 - and no problems.

Update x86_64 system and restarted cjdns which used (locally built) nacl - and no problems.

Seems to work - did not crash when I suspended a session, and it did with the previous version. Using client on Fedora 22 and server on Fedora 23. Abrt assigned the crashes to #1270273

Updated through official Fedora updates-testing, and nothing broke. Now to wait for someone else to install it.

Intel video still tainting kernel: #1303990

Intel video still tainting kernel, but otherwise functional.

tested on x86_64 only.

Tested on X86_64. Would like to test on i386 laptop, but that is f22 and doesn't seem to be in update-testing yet. USB-Wifi memory leak is fixed! Yay!

Intel video still broken for 4.3 series: https://bugzilla.redhat.com/show_bug.cgi?id=1303990

USB Wifi leaks 4-30kb/s kernel memory, depending on bad packets received. If you have USB Wifi, you might want the patched kernel in koji linked here: https://bugzilla.redhat.com/show_bug.cgi?id=1303270

Still a serious memory leak for many people:
https://bugzilla.redhat.com/show_bug.cgi?id=1296972

/proc/meminfo SUnreclaim: grows by 10k/sec resulting in OOM in a few hours.

4.3.3 and 4.3.4 have this regression: https://bugzilla.redhat.com/show_bug.cgi?id=1303270

The system can stay up only 8 hours before crashing with an OOM panic (not due to any user space processes). The BSOD further more leaves the ether nic active in a way that DoSes all devices connected to the same switch.

Stuff seems to work for those 8 hours.