Ubuntu Foundations Development Summary: July 5, 2017
Canonical
on 5 July 2017
This newsletter is 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
- SRU verification policy change – https://lists.ubuntu.com/archives/ubuntu-devel-announce/2017-June/001216.html
- The first server images containing the rolling kernel for 16.04.3 are now available for testing: http://cdimage.ubuntu.com/ubuntu-server/xenial/daily/current/
- We are on our way to python3.6 as default in 17.10; please help us fix the remaining python packages that fail to build: https://lists.ubuntu.com/archives/ubuntu-devel/2017-June/039826.html
The State of the Archive
- OCaml 4.04 transition in progress
- The initial ghc migration for the cycle has completed, another round is now in progress
- The opt-in Artful Alpha 1 was released this week for several flavors. The archive is again unfrozen and packages are proceeding normally.
Upcoming Ubuntu Dates
16.10 EoL in July 2017
16.04.3 point release is scheduled for August 3, 2017
Weekly Meeting
IRC Log: http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-06-29-15.01.moin.txt
Talk to us today
Interested in running Ubuntu in your organisation?
Newsletter signup
Related posts
Canonical Releases Ubuntu 25.04 Plucky Puffin
The latest interim release of Ubuntu introduces “devpacks” for popular frameworks like Spring, along with performance enhancements across a broad range of...
Ubuntu 20.04 LTS End Of Life – activate ESM to keep your fleet of devices secure and operational
Focal Fossa will reach the End of Standard Support in May 2025, also known as End Of Life (EOL). Ubuntu 20.04 LTS has become a critical component for millions...
How we ran an effective sprint to refresh our website, Part 1
Part 1 of how we ran a design sprint to refresh our website. Sharing what worked, what didn’t, and lessons from designing for open source in mind.