Skip to main content
  1. Blog
  2. Article

Canonical
on 5 July 2017

Ubuntu Foundations Development Summary: July 5, 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

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

Related posts

Massimiliano Gori
27 March 2026

Modern Linux identity management: from local auth to the cloud with Ubuntu

Cloud and server Article

The modern enterprise operates in a hybrid world where on-premises infrastructure coexists with cloud services, and security threats evolve daily. IT administrators are tasked with a difficult balancing act: maintaining traditional local workflows while managing the inevitable shift toward cloud-native architectures. Identity has emerged ...

Abdelrahman Hosny
24 March 2026

Canonical welcomes NVIDIA’s donation of the GPU DRA driver to CNCF

Partners Article

At KubeCon Europe in Amsterdam, NVIDIA announced that it will donate the GPU Dynamic Resource Allocation (DRA) Driver to the Cloud Native Computing Foundation (CNCF). This marks an important milestone for the Kubernetes ecosystem and for the future of AI infrastructure. For years, GPUs have been central to modern machine learning and high ...

ijlal-loutfi
23 March 2026

Hot code burns: the supply chain case for letting your containers cool before you ship

Ubuntu Article

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, you’re signing first and asking questions later. In software supply chain security, the freshest code isn’t always the safest. Sometimes the most secure component in your pipeline is ...