Of late I am often noticed changes like these on the bugs that are
assigned to me:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |FutureFeature
Status|NEW |ASSIGNED

The most recent example one such bug is https://bugzilla.redhat.com/469696

I can understand the "FutureFeature" keyword, but why is the status
being changed?

Thanks,
Debarshi

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thu November 6 2008, Debarshi Ray wrote:
> Of late I am often noticed changes like these on the bugs that are
> assigned to me:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
>- Keywords| |FutureFeature
> Status|NEW |ASSIGNED
>
> The most recent example one such bug is https://bugzilla.redhat.com/469696
>
> I can understand the "FutureFeature" keyword, but why is the status
> being changed?

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.

Regards,
Till

[1] https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thursday 06 November 2008 05:59:49 Till Maas wrote:
> On Thu November 6 2008, Debarshi Ray wrote:
> > Of late I am often noticed changes like these on the bugs that are
> > assigned to me:
> >
> > What |Removed |Added
> > -------------------------------------------------------------------------
> >-- - Keywords| |FutureFeature
> > Status|NEW |ASSIGNED
> >
> > The most recent example one such bug is
> > https://bugzilla.redhat.com/469696
> >
> > I can understand the "FutureFeature" keyword, but why is the status
> > being changed?
>
> 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 thought they decided to use something like a "triaged" keyword so that state
is preserved.

https://www.redhat.com/archives/fedora-test-list/2008-October/msg00221.html

-Steve

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Debarshi Ray wrote:

Of late I am often noticed changes like these on the bugs that are
assigned to me:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |FutureFeature
Status|NEW |ASSIGNED

The most recent example one such bug is https://bugzilla.redhat.com/469696

I can understand the "FutureFeature" keyword, but why is the status
being changed?


As Till mentioned, having your bug ASSIGNED is a Good Thing(TM)

If you want to see the details, load the bug in your browser and hit the
"History" link at the top right (next to the "Modified" field). This
takes you to a page that lists every change to the bug, when it was made
and who made it.


The table format it displays in gets somewhat chewed up when pasted into
a mail, but following that link for your bug I can see:


poelstra@redhat.com 2008-11-05 15:32:55 EDT
Keywords FutureFeature
Status NEW ASSIGNED


So, John added the keyword and changed the status from new -> assigned.

Regards,
Bryn.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thu November 6 2008, Steve Grubb wrote:

> I thought they decided to use something like a "triaged" keyword so that
> state is preserved.

It was decided to keep it as it is for the time beeing:

https://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2008-Oct-07#NEW-.3EASSIGNED

Regards,
Till
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Till Maas wrote:

On Thu November 6 2008, Steve Grubb wrote:



I thought they decided to use something like a "triaged" keyword so that
state is preserved.



It was decided to keep it as it is for the time beeing:

https://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2008-Oct-07#NEW-.3EASSIGNED

Regards,
Till

I'd like to suggest that when committees reach decisions with regard to
discussions from this list, the decision is communicated to this list.


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

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@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thu, Nov 6, 2008 at 9:02 AM, shmuel siegel <fedora@shmuelhome.mine.nu> wrote:

> I'd like to suggest that when committees reach decisions with regard to
> discussions from this list, the decision is communicated to this list.

Since there was a decision made NOT to deviate from current policy,
then there was no need to communicate outside of the normal meeting
minutes. If we had made a change to the policy, that would have been
communicated loudly

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thu November 6 2008, Kevin Kofler wrote:
> 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.

I updated the wiki to show this.

Regards,
Till
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thursday, 06 November 2008 at 16:46, Jon Stanley wrote:
> On Thu, Nov 6, 2008 at 9:02 AM, shmuel siegel <fedora@shmuelhome.mine.nu> wrote:
>
> > I'd like to suggest that when committees reach decisions with regard to
> > discussions from this list, the decision is communicated to this list.
>
> Since there was a decision made NOT to deviate from current policy,
> then there was no need to communicate outside of the normal meeting
> minutes. If we had made a change to the policy, that would have been
> communicated loudly

And the current policy is in effect since when, exactly? Is it documented?
Was it announced? I don't seem to recall anyone telling me to use ASSIGNED
if I haven't even started working on a bug.

Regards,
R.

--
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list