public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree
Date: Tue, 12 Jun 2007 14:21:08 +0300	[thread overview]
Message-ID: <466E81A4.1030102@gentoo.org> (raw)
In-Reply-To: <928AE60C-38E1-48C4-9C61-4735D921270E@cilly.mine.nu>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

cilly kirjoitti:
> On Jun 12, 2007, at 12:48 PM, Luca Barbato wrote:
> 
>> Keep in mind that the trade off is :
>>
>> - our time
>> - our sanity
>> - what provide to our used
>> - the quality of what we provide to out users.
>>
>> We all try our best to not burn out while serving you the best we could
>> think.
> 
> Does it make such a difference if ebuilds are kept for a few weeks?

Nope and they should usually be kept but we can't make a hard rule
because there are cases where the old ebuilds don't work any more. If
you find that a broken version slipped the cracks of the arch teams and
made it to stable with the old version removed, file a bug to
bugs.gentoo.org and hopefully the maintainer learns from his/her mistake
of removing it too soon. If the maintainer keeps on doing the same
thing, then you can try to escalate things to qa/devrel. If you are
using ~arch, then encountering some broken stuff is fully expected, just
file a bug and the maintainer is expected to react in a timely manner.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-06-12 11:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  9:40 [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree cilly
2007-06-12  9:49 ` [gentoo-dev] " Christian Faulhammer
2007-06-12  9:53   ` cilly
2007-06-12  9:59 ` [gentoo-dev] " Luca Barbato
2007-06-12 10:04   ` Fernando J. Pereda
2007-06-12 10:01 ` Fernando J. Pereda
2007-06-12 10:14   ` cilly
2007-06-12 10:21     ` Fernando J. Pereda
2007-06-12 10:30       ` cilly
2007-06-12 10:40         ` Marijn Schouten (hkBst)
2007-06-12 10:48           ` cilly
2007-06-12 11:09             ` Marijn Schouten (hkBst)
2007-06-12 10:36   ` Richard Freeman
2007-06-12 10:46     ` Fernando J. Pereda
2007-06-12 10:53       ` cilly
2007-06-12 10:59         ` cilly
2007-06-12 11:27           ` Luca Barbato
2007-06-12 11:37             ` cilly
2007-06-12 11:29           ` Christoph Mende
2007-06-12 11:38             ` cilly
2007-06-13 14:35             ` Robert Buchholz
2007-06-13 14:58               ` Brian Harring
2007-06-12 16:55           ` [gentoo-dev] " Duncan
2007-06-13 14:44             ` banym tuxaner
2007-06-12 11:03         ` [gentoo-dev] " Fernando J. Pereda
2007-06-12 11:08           ` cilly
2007-06-12 16:05         ` Luis Francisco Araujo
2007-06-12 10:48     ` Luca Barbato
2007-06-12 10:50       ` cilly
2007-06-12 11:21         ` Petteri Räty [this message]
2007-06-12 11:50           ` cilly
2007-06-12 11:00     ` Marijn Schouten (hkBst)
2007-06-12 11:25     ` [gentoo-dev] " Christian Faulhammer
2007-06-12 11:52       ` cilly
2007-06-12 12:55 ` [gentoo-dev] " Marius Mauch
2007-06-12 12:59   ` cilly

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=466E81A4.1030102@gentoo.org \
    --to=betelgeuse@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