AHXproject

Why you should retire your Microsoft Azure Consumption Commitment (MACC) with Ubuntu Pro

When your organization first signed its Microsoft Azure Consumption Commitment (MACC), it was a strategic step to unlock better pricing and enable cloud growth. However, fulfilling that commitment efficiently requires planning. Organizations often look for ways to retire their MACC that drive strategic value, rather than simply increasing consumption to meet a deadline.

The goal is to meet your commitment while delivering long-term benefits to the business.

With Ubuntu Pro in the Azure Marketplace, you can retire your MACC at 100% of the pretax purchase amount. In practice, this allows you to meet consumption goals on your standard Azure invoice, while securing your open source supply chain and automating compliance.

Turn a spend target into an open source security strategy

Instead of simply increasing consumption to hit a target, effective IT and FinOps teams align their MACC with broader strategic goals. Open source support and security maintenance is a priority for enterprises, as a recent Linux Foundation report  shows: 54% of enterprises want long-term guarantees, and 53% expect rapid security patching.

Ubuntu Pro offers both. By choosing software that strengthens your security and operations, you can retire your MACC while funding capabilities your organization prioritizes.

Allocating MACC to Ubuntu Pro is a direct investment in your open source estate:

• Expanded Security Maintenance (ESM): extend security coverage to the critical open source applications running above the operating system layer. ESM provides up to 15 years of security updates for the OS, plus tens of thousands of packages. You might already see alerts for these missing updates in your Azure portal – learn how to check your exposure in our blog: [A complete security view for every Ubuntu LTS VM on Azure ].
• Kernel Livepatch: reduce maintenance windows by applying critical kernel patches without requiring a reboot for most workloads.
• Compliance tooling: access options for CIS hardening and FIPS 140-3 validated cryptographic modules to support meeting compliance and regulatory needs.
• Optional enterprise support: add enterprise SLAs, direct access to Canonical engineers for break-fix and bug-fix, and guidance on operating Ubuntu and ESM-covered packages on Azure.

By choosing Ubuntu Pro, you convert your MACC spend into a maintained open source foundation across the development lifecycle.

Maximize value and streamline procurement

Retiring your commitment should be financially efficient and administratively simple. While standard Marketplace listings are MACC-eligible, many organizations use private offers  to secure tailored commercial terms, like custom pricing or volume discounts, without sacrificing eligibility.

We support both standard private offers and multiparty private offers for rollouts involving resellers in the US/UK. In all cases, checking that your purchase counts toward your commitment is straightforward:

• Confirm Eligibility: verify the listing or private offer is marked as "Azure benefit-eligible."
• Purchase Correctly: execute the transaction in the Azure portal under the tenant and subscription tied to your MACC agreement.

This approach guarantees that every dollar spent satisfies your financial goals while delivering the specific security coverage your organization needs.

Ready to align Ubuntu Pro with your MACC? Talk to our team .

Fulfilling your Microsoft Azure Consumption Commitment (MACC) requires efficient planning. Discover how allocating your MACC to Ubuntu Pro allows you to meet consumption goals while securing your open source supply chain and automating compliance.


Source: https://ubuntu.com//blog/retire-azure-consumption-commitment-macc-ubuntu-pro Dec 13, 2025, 02:07 AM

Ubuntu 26.04 Snapshot 2 Available to Download

The second Ubuntu 26.04 snapshot is ready to download, making testing of 'Resolute Raccoon' ahead of next April's stable release easier. Details inside.

You're reading Ubuntu 26.04 Snapshot 2 Available to Download , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Monthly Snapshot, Ubuntu 26.04 LTS
Source: https://www.omgubuntu.co.uk/2025/12/ubuntu-26-04-snapshot-2-released Dec 12, 2025, 06:47 PM

Pop!_OS 24.04 LTS Released with New COSMIC Desktop

Pop!_OS 24.04 LTS is available for download, the first version of the Ubuntu-based Linux distribution to use System76's all-new Rust-based COSMIC desktop environment. It's been a "long ride" to get here (building an entirely new Linux desktop, compositor, widget toolkit, and suite of first-party apps is no mean feat). System76 announced plans to build COSMIC in 2021, and a series of alpha and beta builds followed. Now, it's out in orbit, joining the constellation of Linux distros (cheesy, eh). Carl Richell, Founder and CEO of System76, says the company is "proud of this contribution to the open source ecosystem", and [...]

You're reading Pop!_OS 24.04 LTS Released with New COSMIC Desktop , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Cosmic DE, Distro Release, Pop!_OS
Source: https://www.omgubuntu.co.uk/2025/12/pop_os-24-04-lts-stable-release Dec 11, 2025, 08:49 PM

Thunderbird 146 Update Migrates Logins to AES + More

MZLA Technologies Corporation has released Thunderbird 146, the latest monthly update for its famed open-source email client. Changes this month may sound less flashy compared to last month, which saw Thunderbird 145 add Microsoft Exchange support (albeit with some caveats, carveouts and a couple of capabilities still be added). Plus, work on readying Thunderbird Pro, the paid-for subscription-based webmail, appointment and file sending service excepted to cost upwards of $9/m, for a soft-launch continues. Those services are about to enter community testing. What's New in Thunderbird 146? MZLA say logins are migrated to a more modern AES encryption standard in [...]

You're reading Thunderbird 146 Update Migrates Logins to AES + More , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, App Updates, Thunderbird
Source: https://www.omgubuntu.co.uk/2025/12/thunderbird-146-login-migration Dec 11, 2025, 08:40 PM

Java 25 now available on Google Cloud Serverless

[December 11, 2025] Today Canonical, the publisher of Ubuntu, announced the immediate availability of Java 25 across Google Cloud's serverless portfolio, including Cloud Run, App Engine, and Cloud Functions.

This release is the result of a collaboration between Google Cloud and Canonical, and it will allow developers to access the latest Java features the moment they are released publicly. All three serverless products use Ubuntu 24.04 as the base image, with Canonical actively maintaining the runtime and ensuring timely security patches.

Simplified deployment with Buildpacks

Deploying Java 25 is easy and fast thanks to Google Cloud Buildpacks. You do not need to create manual Dockerfiles or manage complex container configurations.

Buildpacks are designed to transform your source code into a production-ready container image automatically. When you deploy your application, the Buildpacks system detects your requested Java version and automatically provisions the Ubuntu-based Java 25 environment, which Canonical team continuously updates with security fixes. This "source-to-deploy" workflow allows you to focus entirely on writing code while Google Cloud and Canonical handle the underlying OS and runtime security.

Get started

To get started, simply use the GOOGLE_RUNTIME_VERSION environment variable to specify the JDK version to 25.  

pack build java-app –builder=gcr.io/buildpacks/builder  –env GOOGLE_RUNTIME_VERSION=25

To learn more about Canonical support on Java, please read our reference documentation .

More reading and resources

• Runtime support details
• Ubuntu base images
• Learn more about Buildpacks

[December 11, 2025] Today Canonical, the publisher of Ubuntu, announced the immediate availability of Java 25 across Google Cloud's serverless portfolio, including Cloud Run, App Engine, and Cloud Functions. This release is the result of a collaboration between Google Cloud and Canonical, and it will allow developers to access the latest Java features the moment [...]


Categories: Google Cloud, Java, serverless, Ubuntu
Source: https://ubuntu.com//blog/java-25-now-available-on-google-cloud-serverless Dec 11, 2025, 04:38 PM

Ubuntu's New Telemetry Tool to 'Phone Home' Monthly

Changes are afoot for Ubuntu's opt-in telemetry service, including greater transparency with the open-sourcing of the server backend that processes data when users opt-in. Ubuntu 25.10 added Ubuntu Insights, a newer hardware metrics reporting service that's preinstalled alongside the distro's existing Ubuntu Report telemetry tool. The latter used by those who upgrade to 25.10, the former on fresh installs only. But 26.04 LTS coming, having two metric-gathering tools is a bit OTT. Canonical aims to make Insights the default tool for all users, including those who upgrade from an older version where consent was managed by Ubuntu Report (i.e., Ubuntu [...]

You're reading Ubuntu's New Telemetry Tool to 'Phone Home' Monthly , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Canonical, Ubuntu 26.04 LTS, ubuntu report
Source: https://www.omgubuntu.co.uk/2025/12/ubuntu-insights-telemetry-26-04-lts Dec 11, 2025, 05:54 PM

Harnessing the potential of 5G with Kubernetes: a cloud-native telco transformation perspective

Telecommunications networks are undergoing a cloud-native revolution. 5G promises ultra-fast connectivity and real-time services, but achieving those benefits requires an infrastructure that is agile, low-latency, and highly reliable. Kubernetes has emerged as a cornerstone for telecom operators to meet 5G demands. In 2025, Canonical Kubernetes delivers a single, production-grade Kubernetes platform with long-term support (LTS) and telco-specific optimizations, deployable across clouds, data centers, and the far edge.

This blog explores how Canonical Kubernetes empowers 5G and cloud-native telco workloads with high performance, enhanced platform awareness (EPA), and robust security, while offering flexible deployment via snaps, Juju, or Cluster API. We'll also highlight its integration into industry initiatives like Sylva, support for GPU/DPU acceleration, and synergy with MicroCloud for scalable edge infrastructure.

The rise of the cloud-native telco

Telecom decision-makers face immense pressure to evolve their networks rapidly and cost-effectively. Traditional, hardware-centric architectures struggle to keep pace with 5G's requirements for low latency, high throughput, and dynamic scaling. This is where Kubernetes – the de facto platform for cloud-native applications – comes in. Kubernetes brings powerful automation, scalability, and resiliency that allow telcos to manage network functions like software across data centers, public clouds, and far-edge deployments. The result is a more agile operational model: services can be rolled out faster, resources automatically optimized to demand, and updates applied continuously without disrupting critical services. In the 5G era, such agility is essential for delivering innovations like network slicing, multi-access edge computing (MEC), and AI-driven services.

At the same time, Kubernetes opens the door for telcos to refactor their network functions into microservices. Instead of relying on monolithic appliances or heavy virtual machines, operators can deploy cloud-native network functions (CNFs) – essentially containerized network services – that are lighter and faster to roll out than traditional virtual network functions (VNFs). By shifting to CNFs, new network features (whether a 5G core component or a firewall) can be introduced or updated in a fraction of the time, using automated CI/CD pipelines instead of lengthy manual upgrades. This approach helps telcos simplify the migration from legacy systems to a more agile, software-driven network model.

However, adopting Kubernetes for telecom workloads also means meeting rigorous performance and reliability standards. Carrier-grade services like voice, video, and core network functions can't tolerate unpredictable delays or downtime. Telco leaders need a Kubernetes platform that combines cloud-native flexibility with telco-grade performance, security, and support. Canonical Kubernetes answers that call, providing a Kubernetes distribution specifically tuned for telecommunications needs.

Canonical Kubernetes: optimized for cloud-native 5G networks and edge computing

Canonical's Kubernetes distribution has been engineered from the ground up to address the unique challenges of 5G and cloud-native telco cloud deployments. It is a single, unified Kubernetes offering that blends the ease of use of lightweight deployments with the robustness of an enterprise-grade platform. Importantly, Canonical Kubernetes can be deployed and managed in whatever way best fits a telco's environment – whether installed as a secure snap package or integrated with full automation tooling like Juju (model-driven operations) or Kubernetes Cluster API (CAPI). This flexibility means operators can start small at the network edge or scale up to carrier-core clusters, all using the same consistent platform. Notably, Canonical Kubernetes brings cloud-native telco-friendly capabilities in the areas of performance, networking, operations, and support:

High performance & low latency

Real-time linux kernel  support ensures that high-priority network workloads execute with predictable, ultra-low latency, a critical requirement for functions like the 5G user plane function (UPF). In parallel, built-in support for advanced networking (including SR-IOV and DPDK) enables fast packet processing by giving containerized network functions direct access to hardware, dramatically reducing network I/O latency for high bandwidth 5G applications. Together, these features allow cloud-native network functions to meet stringent performance and determinism once only achievable on specialized telecom hardware.

GPU acceleration

Canonical Kubernetes integrates seamlessly with acceleration technologies to support emerging cloud-native telco workloads. It works with NVIDIA's GPU and networking operators to leverage hardware accelerators (GPUs, SmartNICs, DPUs) for intensive tasks. It supports NVIDIA's Multi-Instance GPU (MIG), which expands the performance and value of the NVIDIA's data center GPUs, such as the latest GB200 and RTX PRO 6000 Blackwell Server Edition by partitioning the GPU into up to seven instances, each fully hardware isolated with its own high-bandwidth memory, cache, and streaming multiprocessors. The partitioned instances are transparent to workloads which greatly optimizes the use of resources and allows for serving workloads with guaranteed QoS.

This means telecom operators can run AI/ML analytics, media processing, or virtual RAN computations that take advantage of GPUs and DPU offloading within their Kubernetes clusters – all managed under the same platform. By tapping into hardware acceleration, telcos can deliver advanced services (like AI-driven network optimization or AR/VR streaming) with high performance, without needing separate siloed infrastructure.

Operational efficiency and automation

Day-0 to Day-2 operations are streamlined through automation in Canonical's stack. The distribution supports full lifecycle management – clusters can be deployed, scaled, and updated via one-step commands or integrated CI/CD pipelines, reducing manual effort and errors. Using Juju charms, Canonical's model-driven operations further simplify complex orchestration, enabling teams to configure and update Kubernetes and related services in a repeatable, declarative way. Built-in self-healing and high availability features ensure that the platform can recover from failures automatically, keeping services running without intervention.

This high degree of automation translates into faster rollout of new network functions and updates (with minimal downtime), allowing telco teams to focus on innovation rather than routine ops tasks.

Edge flexibility

Canonical Kubernetes is designed to run from the core to the far edge with equal ease. Its lightweight, efficient design (delivered as a single snap package) results in a low resource footprint, making it viable even on a one- or two-node edge cluster in a remote site. At the same time, it scales up to multi-node deployments for central networks. The platform supports a variety of configurations – from a single node for an ultra-compact edge appliance, to a dual-node high-availability cluster, to large multi-node clusters for data centers – all with the same tooling and consistent experience.

This flexibility allows operators to extend cloud capabilities to edge locations (for ultra-low latency processing) while managing everything in a unified way. In practice, Canonical's solution can power cloud-native telco IT workloads, 5G core functions, and edge applications under one umbrella, meeting the specific performance and latency needs of each environment.

Long-Term support and stability

Canonical backs its Kubernetes with long-term support options far exceeding the typical open-source release cycle. Each Canonical Kubernetes LTS version can receive security patches and maintenance for up to 15 years , ensuring a stable foundation for cloud-native telco services over the entire 5G rollout and beyond. (For comparison, upstream Kubernetes offers roughly 1 year of support per release).

This extended support window means carriers can avoid frequent, disruptive upgrades and rest assured that their infrastructure remains compliant over the long term. Such a commitment to stability is a key reason telecom operators choose Canonical – long-term maintenance provides confidence that critical network workloads will run on a hardened, well-maintained platform for many years.

Cost efficiency and vendor neutrality

As an open-source, upstream-aligned distribution, Canonical Kubernetes has no licensing costs and prevents vendor lock-in. Telcos are free to deploy it on their preferred hardware or cloud, and they benefit from a large ecosystem of Kubernetes-compatible tools and operators. The platform's efficient resource usage and automation also help drive down operating costs – by improving hardware utilization and simplifying management, it enables operators to serve growing traffic loads without linear cost increases. In short, Canonical's Kubernetes offers carrier-grade performance and features at a fraction of the cost of proprietary alternatives, all while keeping the operator in control of their technology roadmap.

Enabling a new wave of cloud-native telco services

Using Canonical Kubernetes, cloud-native telcos can position themselves to innovate faster and operate more efficiently in the 5G era. They can readily stand up cloud-native 5G Core functions, scale out Open RAN deployments, and push applications to the network edge – all on a consistent Kubernetes foundation. In fact, Kubernetes makes it feasible for telcos to transition from traditional VNFs on virtual machines to containerized CNFs, reducing resource overhead and speeding up deployment of network features. This means legacy network applications can be modernized step-by-step and run alongside new microservices on the same platform, avoiding risky "big bang" overhauls.

The result is not only technical efficiency but business agility: operators can launch new services (from enhanced mobile broadband to IoT analytics) in weeks instead of months, respond quickly to customer demand spikes, and streamline the integration of new network functions or vendors.

Early adopters in the industry are already seeing the benefits. For example, Canonical's Kubernetes has been embraced in initiatives like the European Sylva open telco cloud project , in part due to its security, flexibility and long-term support advantages. This momentum underscores that a performant, open Kubernetes platform is becoming a strategic asset for telcos aiming to stay ahead in a competitive landscape. Perhaps most importantly, Canonical Kubernetes lets telcos focus on delivering value to subscribers – ultra-reliable connectivity, rich digital services, tailored enterprise solutions – rather than getting bogged down in infrastructure complexity. It abstracts away much of the heavy lifting of deploying and upgrading distributed systems, while providing the controls needed to meet strict cloud-native telco requirements. The combination of automation, performance tuning, and openness creates a powerful engine for telecom innovation.

Cloud-native at any scale: Canonical Kubernetes meets MicroCloud

At the edge, complexity is the enemy. That's why Canonical Kubernetes pairs naturally with MicroCloud, our lightweight production-grade cloud infrastructure for distributed environments. MicroCloud fits the edge use case extremely well: it is easy to deploy, fully automated, and optimized for bare-metal and low-power sites. Drop it into a telco cabinet, regional hub, or remote data center, and you get a resilient control plane for running Kubernetes, virtualization, and storage with zero overhead.

In such deployments, MicroCloud and Canonical Kubernetes form a tightly integrated stack that brings cloud-native operations to the far edge. Need to orchestrate CNFs next to VMs? Spin up a single-node cluster with high availability? Scale to dozens of locations without rearchitecting? This combo makes it possible, with snaps for simple updates, Juju for full automation, and long-term support built in.

Conclusion: building the future of cloud-native telco on open source Kubernetes

5G and edge computing are reshaping telecom networks, and Kubernetes has proven to be an essential technology powering this evolution.Industrial IoT ,automotive applications  ,smart cities ,robotics , remote health care, and the gaming industry rely on high data transfer, close to real time latency, very high availability and reliability. Canonical Kubernetes brings the best of cloud-native innovation to the telecom domain in a form that aligns with carriers' operational realities and performance needs. It delivers a rare mix of benefits – agility and efficiency from automation, high performance for demanding workloads, freedom from lock-in, and assured long-term support – making it a compelling choice for any telco modernizing its infrastructure.

Telecommunications leaders looking to become cloud-native telcos should consider how an open-source platform like Canonical Kubernetes can serve as a foundation for growth. Whether the goal is to reduce operating costs in the core network, roll out programmable 5G services at the edge, or simply break free from proprietary constraints, Canonical's Kubernetes distribution provides a proven path forward.

Explore further

To dive deeper into how Canonical Kubernetes meets telco performance and reliability requirements, we invite you to read our detailed white paper: Addressing telco performance requirements with Canonical Kubernetes . It offers in-depth insights and benchmark results from real-world cloud-native telco scenarios. Additionally, visit our blogs on Ubuntu.com and Canonical.com for more success stories and technical guides – from 5G network modernization strategies to edge:

• Edge Networking gets smarter: AI and 5G in action
• Canonical releases FIPS-enabled Kubernetes
• Canonical Kubernetes officially included in Sylva 1.5

Visiting MWC 2026?Book a meeting with Canonical  to find out more.

Telecommunications networks are undergoing a cloud-native revolution. 5G promises ultra-fast connectivity and real-time services, but achieving those benefits requires an infrastructure that is agile, low-latency, and highly reliable. Kubernetes has emerged as a cornerstone for telecom operators to meet 5G demands. In 2025, Canonical Kubernetes delivers a single, production-grade Kubernetes platform with long-term support (LTS) [...]


Categories: Cloud Native, kubernetes, Telco 5G
Source: https://ubuntu.com//blog/harnessing-the-potential-of-5g-with-kubernetes-a-cloud-native-telco-transformation-perspective Dec 10, 2025, 05:47 PM

Two Ubuntu Flavours Won't Be LTS Releases Next Year

Not all of Ubuntu's flavours have applied for long-term support status in next year's 26.04 release. Per the outcome of a recent Ubuntu Technical Board meeting, only 7 of the 10 official offshoots are designated LTS releases: — Oh, and the 'oh yeah, that's a flavour' flavour: (No shade; I just always forget about little ol' Kylin). However, two Ubuntu flavours did not apply for LTS status for 26.04: No Ubuntu Unity LTS? Expected in light of challenges facing the distro (there was no Ubuntu Unity 25.10 release) because the incumbent project lead is, reportedly, now busy with higher education. [...]

You're reading Two Ubuntu Flavours Won't Be LTS Releases Next Year , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Flavors, lts, Ubuntu 26.04 LTS
Source: https://www.omgubuntu.co.uk/2025/12/ubuntu-unity-mate-26-04-lts-status Dec 10, 2025, 06:18 PM

The rhythm of reliability: inside Canonical's operational cadence

In software engineering, we often talk about the "iron triangle" of constraints: time, resources, and features. You can rarely fix all three. At many companies, when scope creeps or resources get tight, the timeline is often the first element of the triangle to slip.

At Canonical, we take a different approach. For us, time is the fixed constraint.

This isn't just about strict project management. It is a mechanism of trust. Our users, customers, and the open source community need to know exactly when the next Ubuntu release is coming. To deliver that reliability externally, we need a rigorous operational rhythm internally, and for over 20 years, we have honored this commitment.

Here is how we orchestrate the business of building software, from our six-month cycles to the daily pulse of engineering:


Fig. 1 Canonical's Operating Cycle

The six-month cycle

Our entire engineering organization operates on a six-month cycle that aligns with the Ubuntu release cadence. This cycle is our heartbeat. It drives accountability and ensures we ship features on time.

To make this work, we rely on three critical control points:

• Sprint Readiness Review (SRR): This is where prioritization happens. Before a cycle begins, we don't just ask "what fits?": we ask "what matters?" We go through feedback to find the most valuable engineering opportunities, ensuring we prioritize quality and impact over volume. We don't start the work until we know the scope is worth the effort.

• Product Roadmap Sprint: The SRR culminates in this one-week, face-to-face event. This is the formal moment of truth where we close out the previous cycle and leadership signs off on the plan for the next one. It ensures that every team leaves the room with a clear, approved mandate.

• Midcycle Review: Three months in, we hold a "Virtual Sprint" to check our progress. Crucially, we review any "bad news", in which we immediately identify items that will not ship or are at risk. By addressing what won't happen upfront, leadership can make informed decisions to course-correct immediately rather than letting a deadline slip.

This discipline ensures we stay agile, and that we can adjust our trajectory halfway through without derailing the entire delivery.

The two-week pulse

While the six-month cycle sets the destination, the "pulse" gets us there. A pulse is our version of a two-week agile sprint.

Crucially, these pulses are synchronized across the entire company, on a cross-functional basis. Marketing, Sales, and Support all operate on this same frequency. When a team member says, "we will do it next pulse," everyone, regardless of department, knows exactly what that means. This creates a shared expectation of delivery that keeps the whole organization moving in lockstep.

Sprints are for in-person connection

We distinguish between a "pulse" (our virtual, two-week work iteration) and a "sprint." For us, a sprint is a physical, one-week event where teams meet face-to-face.

We are a remote-first company, which makes these moments invaluable. Sprints provide the high-bandwidth communication and human connection needed to sustain us through months of remote execution.

We also stagger these sprints to separate context. Our Engineering Sprints happen in May and November (immediately after an Ubuntu release) so teams can focus purely on technical roadmapping. Commercial Sprints happen in January and July, aligning with our fiscal half-years to focus on business value. This "dual-clock" system ensures that commercial goals and technical realities are synchronized without overwhelming the teams.

Managing the exceptions

Of course, market reality doesn't always adhere to a six-month schedule. Customers have urgent needs, and high-value opportunities appear unexpectedly. To handle this without breaking our rhythm, we use the Commercial Review (CR) process.

The CR process protects our engineering teams from chaos while giving us the agility to say "yes" to the right opportunities.

• Protection: We don't let unverified requests disrupt the roadmap. A Review Board assesses every non-standard request before we make a promise.
• Conscious trade-offs: If a new request is critical, we ask: "What are we removing to make space for this?" It forces a conscious decision. We review the roadmap and agree on what gets deprioritized to satisfy the new request.

This ensures that when we do deviate from the plan, it is a strategic choice, not an accident.

Quality as a natural habit

Underpinning this entire rhythm is a commitment to quality standards. We follow the Plan, Do, Check, Act (PDCA) cycle, a concept rooted in ISO 9001. While we align with these formal frameworks, it has become a natural habit for us at Canonical.

This operational discipline is what enables up to 15 years of LTS commitment  on a vast portfolio of open source components, providing Long-Term Support for the entire, integrated collection of application software, libraries, and toolchains. Offering 15 years of security maintenance on our entire stack is only possible because we are operationally consistent. Long-term stability is the direct result of short-term discipline.

By sticking to this rhythm, we ensure that Canonical remains not just a source of great technology, but a reliable partner for the long haul.

At Canonical, time is fixed. Ubuntu releases never slip because we run on a strict rhythm: six-month cycles, two-week pulses, and in-person sprints. Every change is deliberate, ensuring stability without losing agility. This discipline is what enables us to provide 15 years of Long-Term Support. Reliability is built into everything we do.


Categories: Business, Canonical, lifecycle, operations
Source: https://ubuntu.com//blog/the-rhythm-of-reliability Dec 10, 2025, 02:22 PM

Ubuntu 26.04 Will Look More Like Vanilla GNOME

Ubuntu's default desktop is about to look more like upstream GNOME than it has in years — but before you panic unduly, I should stress that it will still look (mostly) the same. The Yaru theme team — try saying that several times in a row — has embarked on a refactor of the GNOME Shell stylesheet ("theme") ahead of the next long-term support release, Ubuntu 26.04 LTS, due out in April and shipping with GNOME 50. Rather than continuing to maintain a customised stylesheet for GNOME Shell, it will instead use the default theme and apply the changes it [...]

You're reading Ubuntu 26.04 Will Look More Like Vanilla GNOME , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, adwaita, GNOME, Ubuntu 26.04 LTS, yaru
Source: https://www.omgubuntu.co.uk/2025/12/ubuntu-26-04-yaru-theme-gnome-shell-changes Dec 10, 2025, 01:57 AM