From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] What should be in place before 1.0 release
Date: Sun Oct 14 15:36:01 2001 [thread overview]
Message-ID: <20011014233423.6d54a2be.karltk@prosalg.no> (raw)
In-Reply-To: <3BC9F783.6000300@dofty.zzn.com>
On Sun, 14 Oct 2001 16:37:23 -0400
Blue Lizard <webmaster@dofty.zzn.com> wrote:
> bugzilla _could_ handle this, but while it is technically ready enough
> our development team is in no way prepared to handle the influx of new
> users that would find it a pain in the neck to use.
Then we find something that's easier to use. We really want this to
further Gentoo development, not hamper it. I do not think our current
system with sporadic mails to the gentoo-dev (and sometimes
gentoo-ebuild!) list is good enough.
> A good way for ebuild to handle apps that dont flag/opt well would be
> nice, other than hard coding everything :) Like if a build is known to
> spark out when a given portion is compiled -O3, knock it down to -O2
> (IOW ebuild parses out flags in make.conf and handles wisely, according
> to the writers instructions.)
We already do this some places, but it is tricky and highly error-prone
since it sometimes requires large amounts of bash wizardry. (Look for -Ox
where x > 2, then bump down to two. If x is s, then remove -Ox altogether,
etc).
Then again, the bash wizardry is what we're (not) paid to do. It's just
that I abhor having to maintain tricky code. The tricky part should be
getting the code to be easy to write an maintain, not making tricky code
out of relatively simple problems. </rant>
> > 4) In a related note, we should have a
> > "grace-period"/"codeslush"/"codefreeze" of at least one week where we
do
> > not add new stuff, and do nothing but bug-squashing. We should verify
that
> > *all* ebuilds have been tested, preferrably with *all* their optional
USE
> > arguments.
>
> You are out of your mind. One week? DUDE! This is a 1.0 release of
> what could be a major mainstream linux distribution. One week?
"at least" should be taken to mean "at minimum", "no less than", or
"certainly more wouldn't hurt" ;p
> Yes, and the idea is that up until the very minute that feature freeze
> goes into effect, anything and everything goes on that list. Someone
> gets the slightest little notion of something that'd be cool and POOF!,
> on the list. Just that stuff more whimish than others would be in a
> diff priority class for obvious reasons.
Exactly why I started the wishlist thread, and why I now intend to
maintain a wishlist on our site.
> Who is in charge of evangelism and propoganda right now?
No one in particular, but drobbins is using his connections with IBM's
DeveloperWorks for all it's worth. The rest of the developers are of
course plugging Gentoo whenever (in)appropriate.
Kind regards,
Karl T
next prev parent reply other threads:[~2001-10-14 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 8:38 [gentoo-dev] What should be in place before 1.0 release Karl Trygve Kalleberg
2001-10-14 10:51 ` Dan C
2001-10-14 14:37 ` Blue Lizard
2001-10-14 15:36 ` Karl Trygve Kalleberg [this message]
2001-10-15 3:14 ` Mikael Hallendal
2001-10-15 3:36 ` Blue Lizard
2001-10-15 6:05 ` Mikael Hallendal
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=20011014233423.6d54a2be.karltk@prosalg.no \
--to=karltk@prosalg.no \
--cc=gentoo-dev@cvs.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