public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Preston A. Elder" <prez@gentoo.org>
To: Paul <set@pobox.com>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] State of Developement
Date: Mon, 26 Aug 2002 06:52:19 -0400	[thread overview]
Message-ID: <200208260652.26822.prez@gentoo.org> (raw)
In-Reply-To: <20020826064346.GX5078@squish.home.loc>

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

On Monday 26 August 2002 02:43 am, Paul wrote:
> 	I have noticed that the numbers assigned to each of my
> new bug reports has been advancing at such a high rate over time,
> that I am given to wonder if the developers can keep up. My
> ebuilds especially have seemed to languish lately.
As more users (especially inexperienced and bug-happy ones) use gentoo, more 
bugs get raised, often times to be marked as duplicates or user error.

As for the ebuilds languisihing longer, there are two reasons for this.  
First, we try to give bugs higher priority ... the whole 'clean up your house 
as is before taking in more mess', and
Second, we're gearing up to release gentoo 1.4, which means theres basically 
no new packages being added to the tree unless we want to justify it to 
Daniel Robbins (which makes sense, you dont want to keep introducing more 
problems when your trying to stabalize a release).

> 	How are you guys doing? Do you have any areas that you
> would like us to focus on? (eg. QA) I could squeeze out ebuilds
> regularly, but I tend to wait on those in the pipeline.
re: where to focus on, thats not my domain, however documentation is ALWAYS 
appreciated (developers hate documenting things ;).  As for the new ebuilds, 
you can submit them to bugzilla, just dont expect them to be added to the 
system before 1.4 is released.

> 	I havent checked, but is gentoo-core still closed?
yes, it is.

> Could it be read-only, maybe only in digest form? The more
> I know about where this project is going, the more motivated
> I am to help, rather than say, sitting back on my haunches
> and waiting. (something I have been unable to do so far:)
Why not email Daniel directly about this :)

- -- 
PreZ
Developer
Gentoo Technologies
http://www.gentoo.org

I wish I could change the world, but God won't give me the source code.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9aghoV+1AOejiuzYRAqI6AJ96enDPBj67RGbQPeBwi8lgziWF+wCfSruS
AU1+ZxTLFLfk8aV+KNcQDe8=
=WGmC
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2002-08-26 10:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26  6:43 [gentoo-dev] State of Developement Paul
2002-08-26  7:21 ` Henti Smith
2002-08-26 10:52 ` Preston A. Elder [this message]
2002-08-26 18:01   ` Jeremiah Mahler
2002-08-26 19:28     ` Grant Goodyear
2002-08-26 21:38       ` Dominik Westner
2002-08-26 22:24       ` George Shapovalov
2002-08-27  0:56         ` Daniel Mettler
2002-08-27  3:45           ` George Shapovalov
2002-08-27 14:35             ` [gentoo-dev] 1.4beta compliment, complaint, question, suggestion Fuper
2002-08-27 15:20               ` mike
2002-08-27 20:26               ` Karl Trygve Kalleberg
2002-08-27  2:12         ` [gentoo-dev] State of Developement Evan Read
2002-08-27  1:38     ` Evan Read

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=200208260652.26822.prez@gentoo.org \
    --to=prez@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=set@pobox.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