From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: VPopmail - SUID vchkpw
Date: Wed, 20 Jul 2005 03:13:35 -0700 [thread overview]
Message-ID: <pan.2005.07.20.10.13.34.605650@cox.net> (raw)
In-Reply-To: 20050720070457.GC11608@curie-int.orbis-terrarum.net
Robin H. Johnson posted
<20050720070457.GC11608@curie-int.orbis-terrarum.net>, excerpted below,
on Wed, 20 Jul 2005 00:04:57 -0700:
>> > And as I've mentioned before I'd like MORE reports of packages working
>> > well before they are moved to stable arch. Without those stable
>> > working reports I don't have any means to judge just how much testing
>> > has been done on a package, other than my own use of a package (and as
>> > such I do leave things longer than the 30 days, because I don't
>> > entirely trust them).
>> This sounds like a request for the QA team. I tend to stay away from
>> most ~arch packages simply because most of our systems are live
>> production servers, but I'd be happy to test-drive new ebuilds of
>> vpopmail if it would help get new versions into the stable tree faster.
> In the absence of a proper QA team, users are some of the best
> large-scale QA available. All I'm asking for are reports that a package
> "Works for me". Try the ebuilds out, and send some feedback in.
As a ~arch user (~amd64), and sometimes even a -* and/or hardmasked for
testing user, this is right up my alley, altho I don't use these specific
packages.
What's the best mechanism (other than becoming an AT, which I'm working
on) for a user to report such working ~arch packages, without spamming the
devs working so hard to stabilize them? ATs have specific procedures in
place for marking an ebuild TESTED and requesting moving from unkeyworded
to ~arch, and from ~arch to stable (for amd64 ATs, here:
http://www.gentoo.org/proj/en/base/amd64/tests/index.xml ), but there do
not appear to be any such procedures outlined for normal ~arch users, at
least that' I've come across.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-20 10:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 1:32 [gentoo-dev] Abuse by gentoo developer Casey Allen Shobe
2005-07-20 1:41 ` Mauricio Lima PIlla
2005-07-20 1:42 ` Mike Frysinger
2005-07-20 2:21 ` Nathan L. Adams
2005-07-20 2:20 ` Mike Frysinger
2005-07-20 2:35 ` Allen Parker
2005-07-20 2:17 ` Daniel Goller
2005-07-20 5:43 ` Casey Allen Shobe
2005-07-20 2:43 ` Robin H. Johnson
2005-07-20 5:37 ` [gentoo-dev] VPopmail - SUID vchkpw Casey Allen Shobe
2005-07-20 5:43 ` [gentoo-dev] QA feedback Mike Frysinger
2005-07-20 13:47 ` Chris Gianelloni
2005-07-23 8:06 ` Stuart Longland
2005-07-20 7:04 ` [gentoo-dev] VPopmail - SUID vchkpw Robin H. Johnson
2005-07-20 10:13 ` Duncan [this message]
2005-07-21 0:28 ` Casey Allen Shobe
2005-07-21 2:59 ` Robin H. Johnson
2005-07-21 0:32 ` Mike Frysinger
2005-07-21 5:15 ` Casey Allen Shobe
2005-07-22 8:45 ` [gentoo-dev] " Duncan
2005-07-20 9:54 ` [gentoo-dev] Re: Abuse by gentoo developer Duncan
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=pan.2005.07.20.10.13.34.605650@cox.net \
--to=1i5t5.duncan@cox.net \
--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