[Hamara-devel] Fwd: Bits from the Stable Release Managers

[shirish]

Hi all,
Let me know if something either about the mail or the Debian workflow is 
not clear, will attempt to clear/clarify.


-------- Forwarded Message --------
Subject: Bits from the Stable Release Managers
Resent-Date: Sun, 24 May 2015 20:28:12 +0000 (UTC)
Resent-From: debian-devel-announce at lists.debian.org
Date: Sun, 24 May 2015 21:27:47 +0100
From: Adam D. Barratt <adam at adam-barratt.org.uk>
To: debian-devel-announce at lists.debian.org

Hi,

We've just announced the date for the first Jessie point release [81ANN]
so it seems a good time for a quick recap of the process around updates
in (old)stable.

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

    * The bug you want to fix in stable must be fixed in unstable
      already (and not waiting in NEW)
    * 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. ...+deb8u1) 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)

Please don't post a message on the mailing list and expect it not to get
lost - there must be a bug report against release.debian.org.  Unless
you particularly enjoy crafting bug meta-data, reportbug is generally
the best way of generating your request.

Due to the way that the archive manages uploads to proposed-updates, if
you upload a .changes file which only includes source and
architecture:all packages, please ensure that you rename it to something
other than "_$arch.changes".

Thanks for helping us take care of our stable releases.

Adam,
for the SRMs

[81ANN]
https://lists.debian.org/1432482929.1640.23.camel@adam-barratt.org.uk




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 820 bytes
Desc: not available
URL: <http://lists.hamaralinux.org/pipermail/hamara-devel/attachments/20150525/b408dc53/attachment.sig>