This seems like a good idea -- everything seems to be working pretty
smoothly right now, but it seems like a step in the right direction as
we have more and more "SIG maintained" perl bits (the stuff formerly
belonging to JPO comes to mind). Should we adopt it as our policy
also; that is, when working on a bug for a perl package we toggle the
state to ON_DEV?
-Chris
---------- Forwarded message ----------
From: Kevin Kofler <kevin.kofler@xxxxxxxxx>
Date: Thu, Nov 6, 2008 at 7:18 AM
Subject: Re: Who moved my bug?
To: fedora-devel-list@xxxxxxxxxx
Till Maas <opensource <at> till.name> writes:
> ASSIGNED means, that the bug has been triaged, i.e. it is assigned to the
> rigth component and all necessary information is provided[1]. A member of the
> Fedora Triage Team probably did the changes to your bugs.
I'll also add that if you work in a team and need a status to set when you're
actively working on fixing something (so you don't duplicate work in the team),
you can use the ON_DEV status for that purpose. (KDE SIG and a few other teams
use this.) Note that this is not required, it's only a convention followed by
some team-maintained packages.
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
Chris Weyl
Ex astris, scientia
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list
