public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Riyad Kalla" <rsk@u.arizona.edu>
To: "'Joseph Carter'" <knghtbrd@efn.org>
Cc: <mcummings@datanode.net>, "'Tony Clark'" <tclark@telia.com>,
	<gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] perl again
Date: Tue, 7 Jan 2003 22:27:32 -0700	[thread overview]
Message-ID: <001101c2b6d6$a8c56300$0200000a@rsk> (raw)
In-Reply-To: <20030108024508.GA10878@bluecherry.net>

Yes you have a good point. I'll just bootstap my system, then wait a few
days before emerge kde'ing (so I don't have to compile it 2wice, which
takes slightly longer than eternity)

Best,
-Riyad

-----Original Message-----
From: Joseph Carter [mailto:knghtbrd@efn.org] 
Sent: Tuesday, January 07, 2003 7:45 PM
To: Riyad Kalla
Cc: mcummings@datanode.net; 'Tony Clark'; gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] perl again


On Tue, Jan 07, 2003 at 12:23:42PM -0700, Riyad Kalla wrote:
> Tommorow? So no waiting for KDE? If you guys do release on the 14th,
> that's one day after 3.1 comes out, talk about cutting it close! :)

If I bring one pearl of wisdom from years of involvement with Debian, it
is that you should NEVER hold up the release of something like a Linux
distribution for someone else's product which is due "any day now", even
if that date has been set in stone.

The reasons for this are many and include:

 - Release dates slip, you could be waiting longer than anticipated.
The
   development team is confident that Gentoo will be ready for release
on
   the 14th.  It should release then if it is!  If other things will
come
   along later, then so be it.  It's easyer to add something as an
upgrade
   to what's already released than to hold up the entire release while
it
   is integrated.
 - It's not like you can "just wait a few days more" for it; there's QA
   issues to contend with.  Is the software ready for everyone?  The
   people who released it may think so, but as always Gentoo would need
to
   do its own testing to make sure it does not bork your system for you.
 - If the release is delayed for every "just one more thing" that comes
   along, then a release will never happen.  (Of course, observance of
   this does not seem to help Debian release any faster than if they had
   added every little thing along the way, but I digress quickly..  *g*)

-- 
Joseph Carter <knghtbrd@efn.org>                     glDisable
(DX8_CRAP);
 
We've upped our standards, so up yours!



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-08  5:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 19:14 [gentoo-dev] perl again Tony Clark
2003-01-07 19:21 ` Michael Cummings
2003-01-07 19:23   ` Riyad Kalla
2003-01-08  2:45     ` Joseph Carter
2003-01-08  5:27       ` Riyad Kalla [this message]
2003-01-08  3:11     ` [gentoo-dev] " Brian Jackson
2003-01-07 19:48   ` [gentoo-dev] " Tony Clark
2003-01-07 20:07   ` George Shapovalov
2003-01-08 13:14 ` Michael Cummings

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='001101c2b6d6$a8c56300$0200000a@rsk' \
    --to=rsk@u.arizona.edu \
    --cc=gentoo-dev@gentoo.org \
    --cc=knghtbrd@efn.org \
    --cc=mcummings@datanode.net \
    --cc=tclark@telia.com \
    /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