[haiku-development] Re: Improvements to Icon-O-Matic
- From: "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 25 Jul 2010 09:54:54 +0000
> On Sun, Jul 25, 2010 at 12:16:10AM -0400, Rene Gollent wrote:
> > Unless all the enhancements are tightly focused on the same small
> > area, it's actually much easier/better from a ticket management
> > standpoint to split them up for a number of reasons, most notably
> > that
> > it's easier to take ownership of one small chunk, fix it, and close
> > the ticket so it's clear that it's done. If you have a ticket with
> > a
> > giant laundry list of unrelated enhancements in it, the only way to
> > manage it is to keep a checklist in there, which often will mean
> > anyone wishing to make those changes will have to read through the
> > whole ticket history to figure out what has/hasn't been done. This
> > also it makes ownership less clear, since it becomes less obvious
> > if
> > the current owner of the ticket is actively working on a particular
> > feature or not, and thus makes it more annoying to coordinate not
> > stepping on each other's toes.
>
Not to mention devs are always happy to close a ticket when they are
done. So, more ticket, more happy devs ! :)
> OK. Makes sense. I'll retract my suggestion then... (:-/)
> Might be nice to have that 'laundry list' somewhere, though, to get
> an overview of the app's state -- the wiki, perhaps?
Use the ticket filtering feature of trac, eg :
http://dev.haiku-os.org/query?status=assigned&status=in-progress&status=new&status=reopened&type=enhancement&component=Applications%2FIcon-O-Matic&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority
ions%2FIcon-O-
Matic&col=id&col=summary&col=status&col=type&col=priority&col=milestone
&col=component&order=priority
(All Icon'O'Matic enhancements)
Other related posts: