Ubuntu Foundations Development Summary: August 1, 2017
Canonical
on 1 August 2017

This newsletter is here to provide a status update from the Ubuntu Foundations Team. There will also be highlights provided for any interesting subjects the team may be working on. If you would like to reach the Foundations team, you can find us at the #ubuntu-devel channel on freenode.
Highlights
- Brian Murray announced a change to the behavior of do-release-upgrade -d: https://lists.ubuntu.com/archives/ubuntu-devel/2017-July/039906.html
- OpenJDK 8 has been released with the 8u141 security patches
- Reliability issues in unattended-upgrades have been addressed: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980
- Netplan 0.25 has been released, including test fixes, IPv6 RA fixes, and handling of MTUs with the NM backend
The State of the Archive
- The ocaml 4.04 transition is done
- Ubuntu 16.10 is now EOL
- python3.6 is now the default in artful
- The perl 5.26 transition has started in artful-proposed; expect delays in package migrations while the autopkgtest runners work through the backlog of related tests.
- The transition to gcc 7 as default will begin in early August. https://lists.ubuntu.com/archives/ubuntu-devel/2017-July/039924.html
Upcoming Ubuntu Dates
- 16.04.3 point release is scheduled for August 3, 2017
- 17.10 Feature Freeze – August 24, 2017
Weekly Meeting
Talk to us today
Interested in running Ubuntu in your organisation?
Newsletter signup
Related posts
Modern Linux identity management: from local auth to the cloud with Ubuntu
The modern enterprise operates in a hybrid world where on-premises infrastructure coexists with cloud services, and security threats evolve daily. IT...
Canonical welcomes NVIDIA’s donation of the GPU DRA driver to CNCF
At KubeCon Europe in Amsterdam, NVIDIA announced that it will donate the GPU Dynamic Resource Allocation (DRA) Driver to the Cloud Native Computing Foundation...
Hot code burns: the supply chain case for letting your containers cool before you ship
Zero CVEs doesn’t mean secure. It means unexamined. New code has zero CVEs because no one has studied it yet, and if you’re rebuilding nightly from upstream,...