From: John Davis <zhen@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] 2004.0 Information
Date: Mon, 23 Feb 2004 17:00:36 -0500 [thread overview]
Message-ID: <403A7804.7020303@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all -
As you have probably heard, the formal release for 2004.0 has been
pushed back to Saturday Feb 28 because of GRP testing.
Unless you are x86, this really does not affect you though. If you are
ready to release for your arch, then by all means, please release. The
mirrors are ready. If you want to hit up the major news sites about your
arch's release, go for it. It is your arch, therefore you have complete
control over it :)
The only thing that might affect you is that the formal releng press
release will not be posted until either Saturday or Monday (I am
thinking Monday).
Just make sure that your LiveCDs are in sync with the new layout that
drobbins mailed to the list a couple of days back. The CDs being
formatted that way is the only stipulation for release - they *have* to
follow that format. If you do not have GRP for your arch (mips comes to
mind iirc), then just create the basic CD1 that drobbins outlined.
Thank you all for your patience. I can assure you that 2004.1 will be
less hectic. The first time is always the hardest.
Regards,
//zhen
- --
John Davis
Gentoo Linux Developer
<http://dev.gentoo.org/~zhen>
- ----
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc>
Fingerprint: 2364 71BD 4BC2 705D F338 FF70 6650 1235 1946 2D47
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAOngEZlASNRlGLUcRAu5JAKC1tQz2EFqV54SID2QIDTz7qeJxdACffvBQ
pAGzhJ1CfZtn/NbnlblJmTo=
=tjde
-----END PGP SIGNATURE-----
--
gentoo-releng@gentoo.org mailing list
next reply other threads:[~2004-02-23 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 22:00 John Davis [this message]
2004-02-23 22:11 ` [gentoo-releng] 2004.0 Information Kurt Lieber
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=403A7804.7020303@gentoo.org \
--to=zhen@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