Language Selection

English French German Italian Portuguese Spanish

Bits from the [Debian] Stable Release Managers

Filed under



The Stable Release Managers, with the support of the rest of the
Release Team, are responsible for updates to the stable release (and
oldstable while that suite is also being supported by the Security
Team), via point releases and the stable-updates mechanism [STABLE-

You can see the current status of proposed updates to stable via our
BTS pseudo-package [BTS] and our tracking website. [QUEUE-VIEWER]

First 'buster' point release

The first point release for Debian 10 has been scheduled for 7th
September 2019. That is slightly later after buster's initial release 
than we would normally aim for, but an earlier date has proved
difficult with DebConf and holidays.

A point release for 'stretch', Debian 9.10, will also take place on the
same day.

Following the release of 10.1, we will continue to aim for stable point
releases on an approximately two-month basis, and oldstable every three
to four months.

As always, the first update to a new release is very busy, so we ask
for your patience if you are still awaiting a reply to an upload
request. It may be that an update to your package is deferred to a
later point release purely from a workload perspective; more serious or
more urgent fixes will be prioritised.


Uploads to a supported stable release should target their suite name in
the changelog, i.e. 'buster' or 'stretch'. You should normally use
reportbug and the pseudo-package to send a *source*
debdiff, rationale and associated bug numbers to the Stable Release
Managers, and await a request to upload or further information.

If you are confident that the upload will be accepted without changes,
please feel free to upload at the same time as filing the bug. However if you are new to the process, we would
recommend getting approval before uploading so you get a chance to see
if your expectations align with ours.

Either way, there must be an accompanying bug for tracking, and your
upload must comply with the acceptance criteria below.

Update criteria

Here's a reminder of our usual criteria for accepting fixes. These are
designed to help the process be as smooth and frustration-free as
possible for both you and us.

   * The bug you want to fix in stable must be fixed in unstable
     already (and not waiting in NEW or the delayed queue)
   * The bug should be of severity "important" or higher
   * Bug meta-data - particularly affected versions - must be
     up to date
   * Fixes must be minimal and relevant and include a sufficiently
     detailed changelog entry
   * A source debdiff of the proposed change must be included
     in your request (not just the raw patches or "a debdiff
     can be found at $URL")
   * The proposed package must have a correct version number
     (e.g. ...+deb10u1 for buster or +deb9u1 for stretch) and you
     should be able to explain what testing it has had
   * The update must be built in an (old)stable environment or chroot
   * Fixes for security issues should be co-ordinated with the
     Security Team, unless they have explicitly stated that they
     will not issue an DSA for the bug (e.g. via a "no-dsa" marker
     in the Security Tracker) [SECURITY-TRACKER]

Please don't post a message on the debian-release mailing list and
expect it not to get lost - there must be a bug report against

We make extensive use of usertags to sort and manage requests, so
unless you particularly enjoy crafting bug meta-data, reportbug is
generally the best way of generating your request. Incorrectly tagged
reports may take longer to be noticed and processed.


for the SRMs

Read more

Also: Debian 10.1 Expected For Release In One Month

New Debian Release Next Month

  • Debian ‘Buster’ 10.1 coming in September

    Debian is by far my best choice for a server as I love the stability and dependability. As per Debian lists announcement ,the will release Debian 10.1 on 7th of September 2019. Along with this there is going to be a release for Debian 9.10 as well. As per official Debian , they will try to release a stable release every 2 months . The release was delayed because of the Debian conference 2019

    Debian 10 released earlier had the following included.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Running The AMD "ABBA" Ryzen 3000 Boost Fix Under Linux With 140 Tests

Last week AMD's AGESA "ABBA" update began shipping with a fix to how the boost clock frequencies are handled in hopes of better achieving the rated boost frequencies for Ryzen 3000 series processors. I've been running some tests of an updated ASUS BIOS with this adjusted boost clock behavior to see how it performs under Linux with a Ryzen 9 3900X processor. The AGESA ABBA update has an improved boost clock frequency algorithm along with changes to the idle state handling. This AGESA update should better position AMD Ryzen 3000 processors with the boost clock behavior expected by users with better hitting the maximum boost frequency and doing so more aggressively. Read more

Stable kernels 5.2.16, 4.19.74, and 4.14.145

  • Linux 5.2.16
    I'm announcing the release of the 5.2.16 kernel. All users of the 5.2 kernel series must upgrade. The updated 5.2.y git tree can be found at: git:// linux-5.2.y and can be browsed at the normal git web browser:
  • Linux 4.19.74
  • Linux 4.14.145

Linux Container Technology Explained (Contributed)

State and local governments’ IT departments increasingly rely on DevOps practices and agile development methodologies to improve service delivery and to help maintain a culture of constant collaboration, iteration, and flexibility among all stakeholders and teams. However, when an IT department adopts agile and DevOps practices and methodologies, traditional IT problems still need to be solved. One long-standing problem is “environmental drift,” when the code and configurations for applications and their underlying infrastructure can vary between different environments. State and local IT teams often lack the tools necessary to mitigate the effects of environmental drift, which can hamper collaboration and agility efforts. Read more

Ubuntu-maker Canonical shares top 5 snaps per Linux distribution

All Linux users are the same, right? Oh, hell no! Linux users are a diverse bunch, with differing opinions, tastes, and personalities. In fact, that is probably a contributing factor to the fragmentation of the Linux community. Linux users have lots of options between distributions, desktop environments, and more -- they are not stuck in a box like Windows 10 users. To highlight how different Linux users can be, Canonical has released some data about the installation of snaps, categorized by distro. It chose six of the most popular Linux-based operating systems for its analysis -- Ubuntu, Debian, Fedora, CentOS, Arch Linux, and Manjaro. It then shared the top five most popular snaps for each distribution. Read more