From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Is Gentoo dying?
Date: Sun, 04 Apr 2010 01:52:29 +0200 [thread overview]
Message-ID: <4BB7D4BD.70908@gentoo.org> (raw)
In-Reply-To: <n2jb41005391004030903n7364ad84i2f9f5cb9e129c352@mail.gmail.com>
On 04/03/10 18:03, Alec Warner wrote:
> - date of last commit: Gentoo is fast moving and packages that
> haven't had commits since 200{4,5,6} are probably old, unmaintained
> and may not even compile or run.
> - date of last listed maintainer commit versus last commit:
> Basically if the maintainer hasn't touched the ebuild in a while but
> someone else (herd members?) have, the metadata.xml is probably out of
> date.
Have the result of that analysis collected somewhere?
> The above are all pretty easy to do with the data in the tree. Some
> other useful ideas might be:
> - compare open bugs for the package, when was the last bug for a
> package closed (bugs data kinda sucks for this)
Right, but we can get that working. I have a regex to get package
names from bug titles around that works well. All we need to do is fix
all bug titles ever to contain package names: Could take a whole bugday
or two :-)
> - for a given package in a herd, check the version in the tree
> against freshmeat or similar to see how far behind it is (I think
> someone wrote something for this already, exherbo?)
That's a larger project. GSOC ideas should contain such thing.
> - check imlate to see if keywording is behind (is the maintainer
> filing stablereqs?)
While you mention that: it's the first time I hear a maintainer should
do that. if so can you raise awareness of it and explain the what and
why in another thread on gentoo-dev?
Sebastian
next prev parent reply other threads:[~2010-04-03 23:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 9:16 [gentoo-dev] Is Gentoo dying? Tobias Scherbaum
2010-04-03 9:26 ` "Paweł Hajdan, Jr."
2010-04-03 10:12 ` Tobias Scherbaum
2010-04-03 11:36 ` hardened-sources development (was: Re: [gentoo-dev] Is Gentoo dying?) Thomas Sachau
2010-04-03 9:37 ` [gentoo-dev] Is Gentoo dying? Brian Harring
2010-04-03 10:10 ` Tobias Scherbaum
2010-04-03 9:38 ` Petteri Räty
2010-04-03 19:12 ` Jacob Godserv
2010-04-03 9:40 ` Robin H. Johnson
2010-04-03 9:46 ` Robin H. Johnson
2010-04-03 9:46 ` [gentoo-dev] Is Gentoo a Phoenix? Patrick Lauer
2010-04-03 10:19 ` Tobias Scherbaum
2010-04-03 11:33 ` Richard Freeman
2010-04-03 11:50 ` Petteri Räty
2010-04-04 18:09 ` Denis Dupeyron
2010-04-05 15:33 ` Richard Freeman
2010-04-05 17:21 ` Denis Dupeyron
2010-04-04 20:19 ` Zeerak Mustafa Waseem
2010-04-05 4:24 ` [gentoo-dev] " Duncan
2010-04-03 12:40 ` [gentoo-dev] " Magnus Granberg
2010-04-03 12:18 ` [gentoo-dev][Gentoo Phoenix] " Ben de Groot
2010-04-03 14:40 ` [gentoo-dev] Is Gentoo dying? Roy Bamford
2010-04-03 14:59 ` Tobias Scherbaum
2010-04-03 16:03 ` Alec Warner
2010-04-03 16:24 ` Matti Bickel
2010-04-03 23:52 ` Sebastian Pipping [this message]
2010-04-04 20:48 ` Roy Bamford
2010-04-06 6:24 ` Sebastian Pipping
2010-04-04 1:48 ` Joshua Saddler
2010-04-04 2:40 ` Alec Warner
2010-04-04 4:50 ` Dale
2010-04-05 0:28 ` Jorge Manuel B. S. Vicetto
2010-04-04 8:22 ` Tobias Scherbaum
2010-04-04 10:07 ` Joshua Saddler
2010-04-04 8:25 ` Petteri Räty
2010-04-04 8:44 ` Patrick Lauer
2010-04-04 9:56 ` [gentoo-dev] " Duncan
2010-04-04 10:21 ` George Prowse
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=4BB7D4BD.70908@gentoo.org \
--to=sping@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