From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Testing is not a valid reason to package.mask
Date: Fri, 03 Oct 2008 10:06:39 +0300 [thread overview]
Message-ID: <1223017599.29403.2.camel@localhost> (raw)
In-Reply-To: <20081002222435.35768855@epia.jer-c2.orkz.net>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On Thu, 2008-10-02 at 22:24 +0200, Jeroen Roovers wrote:
> # Gen 2 Developer <someone@gentoo.org> (`date`)
> # Masked for testing.
> >=rofl-cat/omgpkg-ver
>
>
> Please people,
>
>
> if you want to get something tested, then don't mask it.
Stuff with high impact better be masked for initial testing, such as new
versions of gcc, glibc and other parts of toolchain and build system,
and other similar things affecting other packages than itself. ~arch is
in my eyes something that updates shouldn't break vastly - a stable
candidate.
Of course when that initial testing is done with helping users, the
reason could be modified to tell things broke and what the tracking bug
is, or unmasked if it works fine with other packages.
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-03 7:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 20:24 [gentoo-dev] Testing is not a valid reason to package.mask Jeroen Roovers
2008-10-02 20:30 ` Jeroen Roovers
2008-10-02 20:41 ` Jeremy Olexa
2008-10-03 0:56 ` Alec Warner
2008-10-03 1:09 ` Josh Saddler
2008-10-03 2:14 ` Jeroen Roovers
2008-10-03 2:23 ` Dawid Węgliński
2008-10-03 3:16 ` Jeroen Roovers
2008-10-03 7:10 ` Alec Warner
2008-10-03 12:06 ` Thomas Sachau
2008-10-03 17:16 ` Alec Warner
2008-10-03 7:06 ` Mart Raudsepp [this message]
2008-10-03 9:29 ` [gentoo-dev] " Duncan
2008-10-04 5:44 ` Ryan Hill
2008-10-04 11:15 ` Thomas Anderson
2008-10-04 16:53 ` Michal Kurgan
2008-10-08 5:10 ` Iain Buchanan
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=1223017599.29403.2.camel@localhost \
--to=leio@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