public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Torsten Veller <tove@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] metadata revised - removal of packages
Date: Fri, 9 Sep 2005 11:58:21 +0200	[thread overview]
Message-ID: <20050909113006.TA94a0d.tv@veller.net> (raw)

1)
While removing maintainers from metadata i realised (not for the first
time) that i don't understand metadata :/

I thought it might be a good idea to add a new herd (maintainer-needed)
for packages where the maintainer has left. I think it will make it
    easier for bugwranglers to assign bugs
    transparent that the maintainance situation has changed
    trackable

To me maintainer-needed is always a first step before a package gets
masked and removed from the tree.

Well, i was told that adding the maintainer-needed herd is not a good
idea and it is best to remove metadata.xml if no valuable information
remains.

I couldn't find information on that. Can somebody explain?



2)
What is the next step after the last maintainer is removed from metadata.xml?
Well i announced these packages on -dev. Now i can wait some time (how
long?) and then?
-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2005-09-09 10:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09  9:58 Torsten Veller [this message]
2005-09-09 12:24 ` [gentoo-dev] metadata revised - removal of packages Jakub Moc
2005-09-09 12:46 ` Mike Frysinger
2005-09-09 13:29   ` Alec Warner
2005-09-09 13:57     ` Chris Gianelloni
2005-09-09 15:23   ` Diego 'Flameeyes' Pettenò
2005-09-09 16:06     ` Ciaran McCreesh
2005-09-09 13:35 ` Chris Gianelloni
2005-09-09 16:10 ` Ciaran McCreesh
2005-09-09 17:36   ` Mike Frysinger
2005-09-09 17:49   ` Chris Gianelloni
2005-09-09 18:08     ` Ciaran McCreesh

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=20050909113006.TA94a0d.tv@veller.net \
    --to=tove@gentoo.org \
    --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