public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Joseph Warner <warnera6@egr.msu.edu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Hold on portage feature requests
Date: Thu, 28 Jul 2005 12:50:03 -0400	[thread overview]
Message-ID: <42E90CBB.3080403@egr.msu.edu> (raw)
In-Reply-To: <42E90660.4010001@gentoo.org>



Donnie Berkholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Jason Stubbs wrote:
> 
> | The reason behind this is that at approximately two thirds of bugs
> received
> | are feature requests and they are drowning at the real bugs. More
> importantly,
> | the critical bugs are becoming very hard to keep track of. This, at a 
> time
> | when we are focusing on fixing major and critical bugs only so as to
> get the
> | next version completed quicker.
> 
> Are you having a tough time filtering out enhancements in your queries
> or something? I don't understand how feature requests could possibly
> interfere with anything besides other enhancements.
> 

Many of the enhancements aren't marked as such, dev-portage has a lot of 
bugs ( I've been watching it for 4 months ) and they are varied, old and 
  extremely difficult to manage at present.  As long as the bugs are 
still in bugzilla I din't see a problem with them being closed.

> Thanks,
> Donnie
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> 
> iD8DBQFC6QZgXVaO67S1rtsRAqkKAJ4+/fQUkkYaUOXVmYGobLTRh+tHeACcDnHU
> ZsYj4ABIrHcnoYHzLPOWmu4=
> =36q7
> -----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-07-28 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 14:20 [gentoo-dev] Hold on portage feature requests Jason Stubbs
2005-07-28 16:22 ` Donnie Berkholz
2005-07-28 16:50   ` Alec Joseph Warner [this message]
2005-07-31 17:07     ` [gentoo-dev] " R Hill
2005-08-01 11:33       ` Jason Stubbs
2005-07-28 17:38   ` [gentoo-dev] " Brian D. Harring
2005-07-28 18:04     ` Donnie Berkholz

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=42E90CBB.3080403@egr.msu.edu \
    --to=warnera6@egr.msu.edu \
    --cc=gentoo-dev@lists.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