From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Checklists for testers and QA
Date: Thu, 31 Jan 2008 17:40:06 -0800 [thread overview]
Message-ID: <1201830006.31938.5.camel@workbox.quova.com> (raw)
In-Reply-To: <1201221502.9420.19.camel@workbox.quova.com>
On Thu, 2008-01-24 at 16:38 -0800, Chris Gianelloni wrote:
> In the case of Beta and Release, we'll also want to ask people for
> specific information about their environment (hardware, software, etc.)
> that will help us to troubleshoot the issues and focus more energy on
> the worst problems.
So nobody has *any* ideas, at all for this?
It's been a week and there hasn't been a *single* response.
This is everyone's chance to give their input on what we should have
checked on the release media. If you do not speak up now, it isn't
likely that it will get checked.
--
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer
--
gentoo-releng@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-01 1:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 0:38 [gentoo-releng] Checklists for testers and QA Chris Gianelloni
2008-02-01 1:40 ` Chris Gianelloni [this message]
2008-02-01 2:22 ` Denys Fedoryshchenko
2008-02-01 2:50 ` M. Edward (Ed) Borasky
2008-02-01 3:02 ` Andrew Gaffney
2008-02-01 3:06 ` John Alberts
2008-02-01 3:22 ` John Alberts
2008-02-01 8:26 ` Chris Gianelloni
2008-02-01 8:22 ` Chris Gianelloni
2008-02-01 8:58 ` Rémi Cardona
2008-02-01 10:18 ` Markus Hauschild
2008-02-01 14:53 ` M. Edward (Ed) Borasky
2008-02-01 17:01 ` Chris Gianelloni
2008-02-01 6:54 ` Rémi Cardona
2008-02-01 13:53 ` Pacho Ramos
2008-02-01 8:49 ` [gentoo-releng] " Christian Faulhammer
2008-02-01 16:56 ` Chris Gianelloni
2008-02-01 10:37 ` [gentoo-releng] " Nelson Batalha
2008-02-01 22:46 ` [gentoo-releng] Re: [gentoo-dev-announce] " Vlastimil Babka
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=1201830006.31938.5.camel@workbox.quova.com \
--to=wolf31o2@gentoo.org \
--cc=gentoo-releng@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