public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Thu, 10 Mar 2005 14:33:05 -0500	[thread overview]
Message-ID: <1110483185.21812.60.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <42309969.7040402@gentoo.org>

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

On Thu, 2005-03-10 at 21:00 +0200, Alin Nastac wrote:
> Please read what I've wrote above. I said "I receive a new ebuild", 
> wouldn't I?
> You can keep your straight face...

What?

That makes absolutely no sense, so I really can't say anything on it.

> As for ~arch and p.mask, please read again 
> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap4 
> under "Masked packages".

Alright.

"Package.mask is used to prevent merging of packages that are broken,
break something else, or badly need testing before going into ~ARCH
KEYWORDS in the tree."

I would say a package that you've not even tested for functionality
falls under "badly need testing before going into ~ARCH" pretty
squarely.

Now, let's look under the "~ARCH in KEYWORDS" on that same document.

"There is a difference between using package.mask and ~arch for ebuilds.
The use of ~arch denotes an ebuild requires testing."

The word ebuild is even in bold.

Did you even bother reading this before trying to use it to make a
point?

> Yeah, luck, that's for sure! I would be more careful before I would make 
> such implausible statements. I did worked in portage for about 5-6 
> months, you know, and I wasn't idling on IRC! What are the odds to keep 
> being lucky every time ?

Pretty high, apparently.

You are relying 100% on other people to do your testing for you.
Whether it is the upstream authors or the users of the package.

> This disscution is started to be both juvenile and counter-productive. I 
> regret that.

I'm not sure how, but if you're regretting your statements, perhaps you
should put more thought into them before shouting "Fire!" in a crowded
theatre.

> Btw, what is your position, being QA manager and all, regarding 
> http://bugs.gentoo.org/reports.cgi?product=Gentoo+Linux&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A 
> ?

For one, you are now trying to point at *ME* for something?  I'm sorry,
but I don't have to justify myself to you.  I am doing my job properly.

Also, I have nothing to do with the QA project.  I am the QA Manager for
Release Engineering.

Perhaps you should spend all this energy testing your own packages,
rather than trying to point out where you think others are doing wrong
when you don't know what you're talking about.

Also, let's look at that graph.  I would be worried if the number of
bugs that were at REOPEN were growing that fast, but considering the
number of packages being added to the portage tree since October of
2003, I don't see that as being too odd.

> Isn't it one of the top QA's priorities to assure that all known bugs 
> are resolved? Or, as ciaranm's membership to mips, you don't do that 
> part of the QA?

Like I said, you really need to back off.  At this point, you're trying
to pick a fight with me simply because you have no retort.  I'm going to
request this one time from you.  Stop.

There is no need for you to stoop to such immature tactics, and it won't
be tolerated.

Thanks,

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

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

  reply	other threads:[~2005-03-10 19:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  1:55 [gentoo-dev] Please follow keywording policy Jason Wever
2005-03-09  2:00 ` Hasan Khalil
2005-03-09  7:38 ` Alin Nastac
2005-03-09 13:39   ` Stephen P. Becker
2005-03-09 14:50     ` Alin Nastac
2005-03-09 16:22       ` Ciaran McCreesh
2005-03-09 17:38         ` Alin Nastac
2005-03-09 18:38           ` Ciaran McCreesh
2005-03-09 18:56             ` Alin Nastac
2005-03-09 19:10               ` Stefan Schweizer
2005-03-09 19:10                 ` Stefan Schweizer
2005-03-09 21:30                 ` Luis F. Araujo
2005-03-09 22:57                 ` Alin Nastac
2005-03-09 23:27                   ` Stephen P. Becker
2005-03-10  0:50                     ` Donnie Berkholz
2005-03-10  0:18                       ` Daniel Goller
2005-03-09 23:36                   ` Jason Wever
2005-03-09 23:42                   ` Aron Griffis
2005-03-10  7:54                     ` Alin Nastac
2005-03-10  8:27                       ` Ciaran McCreesh
2005-03-10 15:54                         ` Chris Gianelloni
2005-03-10 15:52                       ` Chris Gianelloni
2005-03-10  4:34                   ` Grant Goodyear
2005-03-10  8:36                     ` Alin Nastac
2005-03-10 13:14                       ` Ciaran McCreesh
2005-03-10 16:00                       ` Chris Gianelloni
2005-03-10 19:00                         ` Alin Nastac
2005-03-10 19:33                           ` Chris Gianelloni [this message]
2005-03-10 21:25                             ` John Myers
2005-03-10 15:38                   ` Chris Gianelloni
2005-03-09 19:18               ` Patrick Lauer
2005-03-09 19:43                 ` Stefan Schweizer
2005-03-09 19:56                   ` Patrick Lauer
2005-03-10  0:55               ` Jon Portnoy
2005-03-10  8:07                 ` Alin Nastac
2005-03-09 19:20             ` Chris Gianelloni
2005-03-09 16:37       ` Stephen P. Becker
2005-03-09 16:43   ` Chris Gianelloni
2005-03-09 17:40     ` Alin Nastac

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=1110483185.21812.60.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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