public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Current projects, TODOs and Roadmap
Date: Tue, 23 Jul 2002 20:58:13 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.LNX.3.96.1020723205223.17199B-100000@pluto.prosalg.no> (raw)
In-Reply-To: <20020723122932.16613.qmail@web14302.mail.yahoo.com>


On Tue, 23 Jul 2002, Shanon Loveridge wrote:

> If someone could point me towards a roadmap or a TODO feature list for
> the next release I would appreciate it. 

Such a thing does not exist. The closest thing we have is a Verwilst. He's
our release guru. If Bart gets around to updating his home page, perhaps
you can find something at http://www.gentoo.org/~verwilst/

> Otherwise would someone be able to quickly explain how things are
> organised. 

Mostly, developers either work directly on fixing bugs found
bugs.gentoo.org, or on more general solutions to the bugs that appear. 

And of course, they occasionally create a new ebuild on their own ;)

> Also is there a way to show unassigned bugs in
> bugzilla? As I can't seem to find an option.

All "unassigned" bugs are assigned to "bug-wranglers@gentoo.org", please
help yourself.


Kind regards,

Karl T




      parent reply	other threads:[~2002-07-23 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 12:29 [gentoo-dev] Current projects, TODOs and Roadmap Shanon Loveridge
2002-07-23 18:46 ` George Shapovalov
2002-07-23 18:58 ` Karl Trygve Kalleberg [this message]

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=Pine.LNX.3.96.1020723205223.17199B-100000@pluto.prosalg.no \
    --to=karltk@prosalg.no \
    --cc=gentoo-dev@gentoo.org \
    --cc=karltk@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