The GNU Compiler Collection makes its most ambitious jump in years, Incus proves the LXD fork has legs with a major LTS milestone, and the people who keep npm and Maven Central running finally get a seat at the same table. Here’s what matters today.
GCC 16.1 released — C++20 is now the default, and Algol 68 gets a front-end
The first stable release of the GCC 16 series landed on April 30 and was picked up by LWN’s May 7 edition. The headline change: C++20 is now the default dialect, meaning millions of builds that relied on implicit -std=gnu++17 will need to be aware of the shift. Beyond the default bump, GCC 16.1 adds experimental support for several C++26 features including Reflection (-freflection), Contracts, and expansion statements — giving developers early access to the next generation of the language. Perhaps the most surprising addition is an experimental Algol 68 front-end (ga68), because apparently no language ever truly dies. On the performance side, link-time optimization gets smarter toplevel asm handling, speculative devirtualization now targets general indirect calls, and the vectorizer can handle uncounted loops and early exits. GCC 16 is also the first compiler release with official tuning profiles for AMD’s Zen 6 architecture. For any project with a CI matrix that includes GCC, this is the release where C++20 compliance stops being optional.
Incus 7.0 LTS ships — the LXD fork’s second long-term release, with support through 2031
Stéphane Graber’s post-Canonical container project hit a significant milestone on May 5 with the release of Incus 7.0 LTS, the second long-term support release carrying five years of maintenance through June 2031. The feature list reads like a project that’s found its stride: a built-in S3 listener replaces the previous MinIO dependency for storage buckets, OCI image support (first introduced in 6.3) is now mature, and new storage drivers for LINSTOR and TrueNAS expand the backend options. Clustering gets a proper graceful shutdown mechanism that migrates instances to other nodes, and VM backup gains NBD-based dirty bitmap tracking for efficient incremental snapshots. Minimum requirements have jumped to Linux kernel 6.12 and QEMU 8.2, and CGroup v1 plus iptables-based firewalling are officially deprecated. For anyone who followed the contentious LXD-to-Incus fork in 2023, this release is proof that community-driven forks can not only survive but mature into production-grade infrastructure on their own terms.
Announced May 6, Sonatype (maintainers of Maven Central) joined as a founding member of a new Linux Foundation working group dedicated to the financial, operational, and infrastructure challenges of running public package registries at global scale. The timing is not subtle: open source package downloads approached 10 trillion in 2025 as AI-driven demand, bot traffic, and automated publishing pushed registries well past what volunteer infrastructure was designed to handle. The working group’s objectives include developing shared funding models, coordinating security practices across registries, crafting standardized policy frameworks, and producing educational content about what it actually costs to keep these systems running. As Sonatype CTO Brian Fox put it, registries are “operational and security-critical systems sitting in the path of nearly every modern software build.” The uncomfortable truth is that some of the most critical infrastructure in all of software — the systems that resolve your npm install and mvn dependency:resolve — have been running on a mix of corporate goodwill, donations, and sheer stubbornness. This working group won’t fix that overnight, but getting registry operators in the same room with a shared mandate is a necessary first step.
Microcks promoted to CNCF Incubating — the API mocking and testing platform levels up
The CNCF Technical Oversight Committee voted on May 3 to promote Microcks from Sandbox to Incubating status, with the announcement going live May 7. Microcks turns API contract documents — OpenAPI specs, AsyncAPI specs, gRPC/Protobuf definitions, GraphQL schemas, Postman collections, or SOAP/WSDL projects — into live mock servers, and uses those same artifacts to power automated contract conformance tests against real implementations. If you’ve ever set up a mock server by hand to unblock a frontend team waiting on a backend API, you understand the problem this solves. The promotion to Incubating signals that Microcks has passed the CNCF’s due diligence on adoption, governance, and community health — it joins the tier of projects that organizations can reasonably bet on for production use. In a cloud-native world where the number of internal APIs grows faster than the teams building them, standardized mocking and contract testing is the kind of infrastructure that prevents integration hell at scale.
The first point release of the Mesa 26 series shipped May 6 with a wide spread of improvements across Intel, AMD, and NVIDIA’s open-source GPU drivers. The highlights include new Vulkan driver extensions for Intel ANV and AMD RADV, low-latency encode/decode for RADV Vulkan Video, Rusticl OpenCL improvements, experimental Intel Nova Lake P support, and OpenGL ES 2.0 for PowerVR GPUs via the Zink driver. Intel’s i915 Iris, Crocus, and ANV drivers gained VirtIO-GPU native-context support for faster GPU paravirtualization in VMs. There’s also continued work on KosmicKrisp, the Vulkan-on-Metal translation layer. But the release also carries a deprecation notice worth watching: VirGL, the accelerated graphics layer for virtualized environments, is no longer considered maintained and may be removed if nobody steps up. For Linux desktop and gaming users, Mesa releases are the unglamorous engine behind every frame — and 26.1 is a solid incremental step forward.
2026 State of Open Source Report: vendor lock-in concerns surge 68% as open source becomes “a given”
The annual State of Open Source Report from Perforce OpenLogic, OSI, and the Eclipse Foundation dropped this week, with OSI Executive Director Duane O’Brien hosting a May 7 webinar to discuss the findings. Based on 700+ survey responses across industries and regions, the headline number is striking: 98% of organizations increased or maintained their open source usage in the past year, but — and this is the more interesting signal — the percentage reporting unchanged usage hit its highest point ever. Open source isn’t growing because it’s trendy; it’s stabilizing because it’s infrastructure. The sharpest year-over-year change was in vendor lock-in concerns, which surged 22 percentage points to 55% of respondents — a 68% increase driven heavily by European organizations responding to digital sovereignty pressures. Meanwhile, 60% of large enterprise respondents report spending half or more of their time on maintenance and bug fixes rather than new development. The report paints a picture of an ecosystem that has won the adoption battle but is now grappling with the operational reality of running open source as critical business infrastructure — a theme that connects directly to the package registry sustainability effort above.