The snapd roadmap
Gustavo Niemeyer
on 6 September 2017
This article originally appeared at snapcraft forums
released
snapd 2.27 (topic1)
snapd 2.28
Improved configuration get output (topic)
Internal xdg-open implementation (topic3)
Refresh hook support (topic)
Lazy registrations on classic (topic3)
Service control on snap command (start/stop/etc) (topic3)
Schedule
![]() |
beta | Sep 4th |
![]() |
candidate | Sep 25th |
![]() |
stable | Oct 2nd |
snapd 2.29
Service control on snapctl (start/stop/etc) (topic5)
Polkit-based authorizations (topic4)
Fix classic flag on reverts (topic1)
Schedule
![]() |
beta | Oct 2nd |
![]() |
candidate | Oct 23rd |
![]() |
stable | Oct 30th |
upcoming
Base snaps (topic5)
Layouts (curstom mount points) (topic2)
Epochs (stepped upgrades) (topic1)
Repairs (emergency fixes) (topic1)
Command-not-found support (topic?)
Interface hooks (topic1)
Monthly refresh scheduling (topic2)
Timer services (topic1)
Desktop theme support (topic3)
Snapshots (topic)
Multi-user/group support (topic1)
Fix snapd restart on reverts (topic)
Support devmode refreshes (topic)
Interface for locking screen (topic)
Support for wayland sockets (topic)
Service survival across refreshes (topic)
Interfaces in classic snaps (topic)
(other upcoming3 topics)
backlog
Install snap multiple times
Health checks
Entitlements
Talk to us today
Interested in running Ubuntu in your organisation?
Newsletter signup
Related posts
Building an open source chain of trust: new research uncovers key blockers and ways forward
Canonical is pleased to share its latest research report, “The open source chain of trust.” Based on a survey of 500 DevOps professionals, the report...
Beyond safety and security: Why automotive open source demands dependability
In the traditional automotive world, teams often work in silos: the cybersecurity experts lock down the ports, the quality assurance teams hunt for bugs, and...
DirtyClone Linux kernel local privilege escalation vulnerability fixes available
On June 25, 2026, JFrog published their research into CVE-2026-43503, referring to the vulnerability as DirtyClone. The vulnerability had previously been...