From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Thu, 10 Mar 2005 09:54:56 +0200 [thread overview]
Message-ID: <422FFD50.7020904@gentoo.org> (raw)
In-Reply-To: <20050309234242.GB15846@time.flatmonk.org>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
Aron Griffis wrote:
>Alin Nastac wrote: [Wed Mar 09 2005, 05:57:15PM EST]
>
>
>>No gentooer
>>expects from a ~arch ebuild to be stable, so the sky would not fall if
>>you made a mistake and release it under this keyword. When I hear "I
>>cannot mark foo library as ~arch because I don't know how to test it"
>>smells like excuse to me.
>>
>>
>
>Earlier you said that you mark ebuilds stable after 30 days with no
>bugs. Now you're suggesting that marking ~arch by mistake isn't a big
>deal. I don't wish to beat up on you further, but this viewpoint can
>lead to stable ebuilds in the tree that don't even build over the
>course of one month (other than February ;-)
>
>
>
I always test unpack/compile/install functionality of the ebuild before
submittion, even if the submittion means only a script change.
So, from my point of view, every ebuild of mine at least must get
installed. Of course, it doesn't mean that install process will succeed
on any other machines than mine...
I'm only saying that no one will take your head if you do a mistake, but
when you're not doing nothing because you are fearing of a mistake -
this is problem. To err is human, you know.
As for marking an ebuild stable over a month, this is the ideal case. On
average, I mark an ebuild stable on x86 after 2 months.
Again, I want to emphasize that I didn't break anything in portage tree,
even if I have a "shoddy" attitude regarding Gentoo's QA.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-03-10 7:55 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 [this message]
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
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=422FFD50.7020904@gentoo.org \
--to=mrness@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