public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS
Date: Thu, 26 Aug 2004 10:16:10 -0400	[thread overview]
Message-ID: <1093529769.2653.23.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20040825232048.3eca43f3@voyager.weeve.org>

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

On Thu, 2004-08-26 at 01:20, Jason Wever wrote:
> Personally, I would rather run into a package breaking in a revbump than
> have it be missing keywords and not notified that it was behind. While yes
> this stinks from a QA perspective, it also gets the problem addressed and
> resolved quicker (usually) than running into it later on down the road. 
> It's also a lot easier wrt the overhead the package maintainers, arch
> maintainers and infrastructure maintainers have to go through to
> accomidate extra emails, bugs, etc if test requests had to be issued each
> time a package got rev or version bumped in the portage tree.

So for Sparc, I should just KEYWORD away (on non-critical packages) and
hope nothing breaks?

(Though I will be testing on my U2 once I get my hard drive in for it.)

-- 
Chris Gianelloni
Release Engineering - Operations/QA Manager
Games - Developer
Gentoo Linux

Is your power animal a penguin?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-08-26 14:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  1:11 [gentoo-dev] Ebuild bumping policy wrt KEYWORDS Jason Wever
2004-08-25  3:00 ` Jason Wever
2004-08-25 15:30   ` Michael Kohl
2004-08-26  3:17     ` Jason Wever
2004-08-26 14:51       ` Carsten Lohrke
2004-08-26 15:04         ` Ciaran McCreesh
2004-08-26 15:30           ` Carsten Lohrke
2004-08-26 15:33             ` Ciaran McCreesh
2004-08-26 16:11               ` Travis Tilley
2004-08-31 13:07                 ` foser
2004-09-01  2:09                   ` Travis Tilley
2004-09-01 10:06                     ` foser
2004-09-01 16:30                       ` Robert Moss
2004-09-01 23:15                         ` Carsten Lohrke
2004-09-01 23:20                           ` Ciaran McCreesh
2004-09-01 23:42                             ` Carsten Lohrke
2004-08-26 16:27               ` Carsten Lohrke
2004-08-31 13:23           ` foser
2004-08-25 13:51 ` Chris Gianelloni
2004-08-26  3:22   ` Jason Wever
2004-08-26  4:49     ` Donnie Berkholz
2004-08-26  5:20       ` Jason Wever
2004-08-26  6:19         ` Donnie Berkholz
2004-08-26 14:16         ` Chris Gianelloni [this message]
2004-08-26 14:44           ` Ciaran McCreesh
2004-08-26 15:02             ` Chris Gianelloni
2004-08-26 15:31           ` Jason Wever

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=1093529769.2653.23.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@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