Triaging aRTS bugs
jospoortvliet at gmail.com
Mon Jan 7 12:37:16 GMT 2008
On Jan 7, 2008 1:16 PM, Matt Rogers <mattr at kde.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Jan 6, 2008, at 11:31 PM, George Goldberg wrote:
> > Hi all,
> > I am trying to help with triaging out what cruft I can from
> > bugs.kde.org
> > and am wondering what the best approach to take is with 'arts' bugs.
> > As far as I am aware (please correct me if any of this is wrong),
> > its unmaintained and pretty much dead. and, since phonon has replaced
> > it for KDE 4, its unlikely to be revived.
> > Assuming the above is correct, I propose that each of the bugs and
> > feature
> > requests filed on bugs.kde.org for arts should either be reassigned to
> > phonon, or closed (depending on whether they are relevant to phonon or
> > not, since many of them will not be... since phonon != a sound
> > server).
> > I am also volunteering to do this :-)
> > Before I start, are there any objections or suggestions for
> > a better way of going about this?
> > George
> The best approach to take for arts bugs is to do nothing. arts is not
> phonon and so moving those bugs from arts to phonon is not the
> correct thing to do IMHO.
> If you want to help triage bugs, the triage a maintained component.
Getting rid of bugs is a good thing either way, I guess, though you
are right that managed components need more triaging. Situations like
this one are why I'm in favor of closing bugs older than say 12 months
automatically unless the reporter or someone else can confirm the bug
is still relevant.
> - --
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> -----END PGP SIGNATURE-----
More information about the kde-core-devel