From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Cc: gentoo-releng@gentoo.org, gentoo-releng@robin.gentoo.org
Subject: [gentoo-releng] Snapshot and catalyst!
Date: Fri, 03 Jun 2005 14:37:03 -0400 [thread overview]
Message-ID: <1117823824.30756.5.camel@cgianelloni.nuvox.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
It's that time again, folks! Time to brush off the old build boxes and
start working on the next release! Well, this time around, we're going
to be starting *way* early to try to rule out any problems that might
exist before they hold us up.
Anyway, without any further ado (or fanfare) allow me to point all of
you to the snapshot at http://dev.gentoo.org/~wolf31o2/snapshot for your
building pleasure. The MD5 is d1b2846e1d0e63492fc3bfca273f4bab and the
date stamp is 20050603.
I would also like for everyone to test the new catalyst versions before
I unleash them. I'm trying to get rid of the bugs *before* I make a new
catalyst release. The catalyst versions are 1.1.10_pre* and should be
in portage, but package.mask'd. One note of warning, be absolutely sure
that you're running the latest one before mentioning any bugs. Also, I
really do not want bug reports on the pre-release versions, but rather
just emails.
The current catalyst going into portage right now is catalyst
1.1.10_pre3.
(Sorry if this shows up more than once, my email is being a pain)
--
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 --]
reply other threads:[~2005-06-03 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1117823824.30756.5.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-releng@gentoo.org \
--cc=gentoo-releng@lists.gentoo.org \
--cc=gentoo-releng@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