From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Release Engineering Status Update
Date: Wed, 15 Jun 2005 09:12:11 -0400 [thread overview]
Message-ID: <1118841131.14164.2.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1118762538.24889.5.camel@cgianelloni.nuvox.net>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On Tue, 2005-06-14 at 11:22 -0400, Chris Gianelloni wrote:
> In response to Patrick's request for status updates, I'm posting the
> current Release Engineering status.
>
> Release Engineering is well into doing QA and testing for 2005.1 on x86,
> amd64, ppc, ppc64, ia64, and alpha. We are currently testing a new
> version of livecd-tools, catalyst, and genkernel, all of which are
> masked in the tree. We have been on a massive bug-squashing session to
> try to solve any problems before we start building the final release.
I forgot to mention that sparc is also doing their QA.
> Once we work out the few blocking issues we are reaching now, such as
> the perl->ssl issue Robin was talking about, then we will build a "beta"
> release for 2005.1, which we will start selecting groups of users,
> mostly people who filed bugs against 2005.0, to help us with testing,
> specifically on platforms or hardware which we do not possess ourselves.
--
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 --]
prev parent reply other threads:[~2005-06-15 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 15:22 [gentoo-releng] Release Engineering Status Update Chris Gianelloni
2005-06-14 20:38 ` Nathaniel McCallum
2005-06-14 21:47 ` Chris Gianelloni
2005-06-15 13:12 ` Chris Gianelloni [this message]
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=1118841131.14164.2.camel@cgianelloni.nuvox.net \
--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