public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John Davis" <zhen@gentoo.org>
To: <gentoo-releng@lists.gentoo.org>
Subject: [gentoo-releng] 2004.0 release update[Message Scanned]
Date: Fri, 30 Jan 2004 10:50:53 -0500	[thread overview]
Message-ID: <401A7D5D.8050404@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all:
Just some updates on what is going on with 2004.0. First of all, thank
you to everyone for being patient during this process. The product of
your hard work and attention to detail will not go unnoticed by our
users. 2004.0 will mark a new generation of Gentoo; we are definitely
headed forward.

There are some still some issues that need to be taken care of before
release. First, profiles need to be updated to no longer use 1.4 but
rather 2004.0 as their version stamp. I have created a HOWTO that will
ease this process. Please note that updating the profile link *does not*
require a rebuild of your stages - at the very least all that you have
to do is unpack both your portage snapshot and stage tarballs to add the
new profile directory and update the /etc/make.profile symlink.
HOWTO:

<http://www.gentoo.org/proj/en/releng/release/2004.0/releng/profile-update.xml>

Next, I would like to make February 7th the last date that packages can
be marked stable to be included in the release (I will send a mail to
- -core as well). As a reminder, February 7th is not a release deadline,
but rather a date that other developers can use as a benchmark. I know
that some arches have started their final build (ie sparc), and I in no
way want to interfere with that. If your arch is ready to release
2004.0, please do so at your discretion. For x86*, I would like to see a
release by the end of the month, but for ppc, sparc, mips, etc, I will
leave the date up to the respective arch leads. Your arch is your show :)

That should do it for now. As always, if you have any questions, please
get a hold of me. Also, for tracking reasons, please place all catalyst
bugs on bugs.g.o and assign them to release@gentoo.org.

Cheers,
//zhen
- --
John Davis
Gentoo Linux Developer
<http://dev.gentoo.org/~zhen>

- ----
Knowledge can be more terrible than ignorance if you're powerless to
change your world.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAGn1dZlASNRlGLUcRAmwyAKC4KyEQzS8GyAEVMNlkRyuMbaIK/ACdFn27
fwNaY3mQdgcCyfS8qbiuWMU=
=HXds
-----END PGP SIGNATURE-----


--
gentoo-releng@gentoo.org mailing list


                 reply	other threads:[~2004-01-30 15:49 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=401A7D5D.8050404@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