Heya,

On Thursday 27 Jan 2005 23:38, Tim Yamin wrote:
> > I really don't want to be sending this out, but at this point I feel
> > that I must.  As it stands now, I see no way that we can possibly
> > release 2005.0[1] without significant delays.  First off, I want to say
> > that the following complaints and reasons for the delay do not
> > necessarily reflect on everyone involved in the release process.  I am
> > omitting any names to protect the innocent and to keep the guilty from
> > feeling like complete asses.
>
> Our Itanium box at OSU has also decided to get arcane RAM failure right
> now so IA64 stages are getting delayed, hopefully only for a few days
> from $today, until I can either get another box ready or get this one in
> a working state (problem is, the OSU staff have things to do too so it
> might take some time to get a timeslot where stuff can get fixed).
>
> > Release Engineering needs both an Operations Lead and a QA Manager.
> > Experience with the release process and catalyst is definitely preferred
> > and the ability to deal with a bunch of bullshit is a must.
>
> I've agreed to help Chris out for the former. We really need as many
> people as we can *really* testing our releases (read, testing the media,
> and *even* more importantly testing the stages and bootstrapping as that
> is what matters most; working boot media but hosed stages are no good
> for anybody). If you could help just reply and we'll prod you when we
> have testing material for you.
>
> Thanks!

I'll happily test the stages into the ground, and bootstrap the hell out of 
one of my boxes ;-), but I've only got x86 (P4) hardware to hand..  Is there 
anything specific that needs to be tested in light of that?

Also, on the topic of getting more thorough testing, would it be possible to 
get something on the g.o front page and/or #gentoo /topic?  There's probably 
quite a few users who'd help out if they knew where to fetch the 
snapshots. :-)

Best,
Elfyn

-- 
Elfyn McBratney
beu on irc.freenode.net/savannah.[non]gnu.org

PGP Key ID: 0x456548B4
PGP Key Fingerprint:
  29D5 91BB 8748 7CC9 650F 31FE 6888 0C2A 4565 48B4

Attachment: pgpdovH4gRAlf.pgp
Description: PGP signature

Reply via email to