From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from athena.rearviewmirror.org (sense-sea-CovadSub-0-150.oz.net [216.39.147.150]) by chiba.3jane.net (Postfix) with ESMTP id 8C6CAAC6A8 for ; Tue, 22 Oct 2002 14:15:56 -0500 (CDT) Received: from matt by athena.rearviewmirror.org with local (Exim 3.35 #1 (Debian)) id 1844VJ-0006SE-00 for ; Tue, 22 Oct 2002 12:15:49 -0700 Date: Tue, 22 Oct 2002 12:15:49 -0700 To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Re: When is Gentoo 1.4 going to be released? Message-ID: <20021022191549.GA24779@rearviewmirror.org> References: <20021021203305.GE20577@freedom.gentoo.org> <006e01c279df$bee790b0$8204dca7@northamerica.corp.microsoft.com> <3DB5A6D8.2070108@fastwebnet.it> <3DB59715.455ADC02@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DB59715.455ADC02@yahoo.com> User-Agent: Mutt/1.3.28i From: Matt Beland Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 469a84a7-2a75-40ad-877b-f7365fa0263b X-Archives-Hash: e1439e580efedd9612137244b7ba52dc On Tue, Oct 22, 2002 at 02:21:09PM -0400, 3.2.3 wrote: > whoa right there. a lot of people are on crack, too. especially where > concerns a bunch wondering when someone is going to hurry up and give > them something for free. Wrong. We're not asking for the Gentoo team to hurry up and give us our free candy. We want the Gentoo team to let us know when they're going to let us take full advantage of the portage system again. Frankly, I (and I suspect most others) could care less about the 1.4 release in and of itself. Sure, a new version of the compiler and so on would be nice, but I can get that on my own if necessary. The problem is that the portage tree is frozen waiting for 1.4, and has been for some time. Do a 'grep freeze /usr/portage/profiles/package.mask' sometime. That's probably an inaccurate count - on the low side - and I see 14 ebuilds that are masked waiting for the freeze to be over. How many others are not even in the tree? I see a number of the "freeze" comments indicating they were only added to the tree for bugfix testing or because the new build fixes a major bug. > enough software in this world is tossed over the fence according to a > schedule. i don't need any more software that was developed to a > schedule. i've got enought of that at work. i need software that is > actually ready when it is ready, whenever that is. i'm glad there is > some. eye on the ball, not some bean counter's stopwatch. Well, see, here's the thing - that's not what we're asking for. We can't really participate in the internal development - the bugs are available, but we don't know what's being done about them. We don't know if our work would be a duplication of effort, or a wrong track, or not really useful. So we *can't* help fix the problems. At the same time, we get no communication on how things are progressing - are we getting close? Is it months away? Has the entire development team gone on vacation? I need software that's "actually ready when it is ready" too. So when I'm dealing with an Open Source software distribution, I have to wonder why releases are so far apart and include so little community communication and involvement. -- Matt Beland matt@rearviewmirror.org http://www.rearviewmirror.org