From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DATE_IN_PAST_12_24, DMARC_MISSING,INVALID_DATE,MAILING_LIST_MULTI,NICE_REPLY_A autolearn=unavailable autolearn_force=no version=4.0.0 Received: from janus.prosalg.no ([213.236.139.1] helo=io.adm.prosalg.no) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 15ssud-00016k-00 for gentoo-dev@cvs.gentoo.org; Sun, 14 Oct 2001 15:35:11 -0600 Received: from b223a.studby.ntnu.no ([129.241.126.223] helo=motvind) by io.adm.prosalg.no with asmtp (Exim 3.33 #1 (Debian)) id 15ssnh-0007yZ-00 for ; Sun, 14 Oct 2001 23:28:01 +0200 From: Karl Trygve Kalleberg To: gentoo-dev@cvs.gentoo.org Subject: Re: [gentoo-dev] What should be in place before 1.0 release Message-Id: <20011014233423.6d54a2be.karltk@prosalg.no> In-Reply-To: <3BC9F783.6000300@dofty.zzn.com> References: <20011014163620.626d13c5.karltk@prosalg.no> <3BC9F783.6000300@dofty.zzn.com> X-Mailer: Sylpheed version 0.6.2 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org X-Reply-To: karltk@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Sun Oct 14 15:36:01 2001 X-Original-Date: Sun, 14 Oct 2001 23:34:23 +0200 X-Archives-Salt: 5da79adf-0897-4ba4-8e44-4ab88f012822 X-Archives-Hash: 376464be2e89d7628db4be54726ba1a9 On Sun, 14 Oct 2001 16:37:23 -0400 Blue Lizard 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. > > 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