public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Early stabilisation
Date: Tue, 15 Apr 2008 22:46:19 +0200	[thread overview]
Message-ID: <20080415224619.387012bc@epia.jer-c2.orkz.net> (raw)

     Dear ebuild maintainers,


thirty days is the norm for the minimal period between an ebuilds last
non-keywording change while in the tree and the usual call for
stabilisation. If you cannot find a pressing reason to push
stabilisation forward, then don't ask. In the last few days I have seen
several early calls for stabilisation (bugs #217148, #217845, #217841
and #217839 for instance) where no adequate reason was given, in my
opinion.

A good reason might be an important fix of a severe bug, a fix for a
build problem that couldn't be applied to a stable version but had to
go into an ebuild revision, or a version/revision that fixes a security
problem.

On the other hand, maybe these early stabilisation bug reports are a
sign of the times and we need to shorten the normal thirty day period,
become even more of a cutting edge distro - or at least discuss the
options.


Kind regards,
     JeR
-- 
gentoo-dev@lists.gentoo.org mailing list



             reply	other threads:[~2008-04-15 20:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 20:46 Jeroen Roovers [this message]
2008-04-16  9:49 ` [gentoo-dev] Early stabilisation Vlastimil Babka
2008-04-16 14:37   ` Richard Freeman
2008-04-16 19:09   ` Chris Gianelloni
2008-04-16 19:36     ` Samuli Suominen
2008-04-17  7:43       ` Vlastimil Babka
2008-04-17 12:33         ` Samuli Suominen
2008-04-17 17:35           ` Jeroen Roovers
2008-04-17 17:38           ` Jeroen Roovers
2008-04-17 18:04             ` Chris Gianelloni
2008-04-17 18:20               ` Jeroen Roovers
2008-04-17 19:40           ` Santiago M. Mola
2008-04-17 21:51             ` Thomas Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080415224619.387012bc@epia.jer-c2.orkz.net \
    --to=jer@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox