[wp-hackers] Probably best to move tickets to 2.7 instead

James Davis james at freecharity.org.uk
Mon Mar 10 14:06:44 GMT 2008

Chris Johnston wrote:
> Jarad, what I was saying is that until they are assigned a milestone, they go into the "bug," "enhancement," etc just to make it that much easier to distinguish between. (if milestone=null then sort by type) Then when whoever it is that monitors for emergent items only has to look in the bugs group. Once they are assigned to a milestone though, they go to the milestone that they are assigned and out of the general categories. Basically, I think that having one folder called "future" would put way too many tickets into it to make it easy to go through and see what someone might want to work on.

I the usual pre-release discussion will simply change to "There's a new 
release due out soon and hardly any bugs have been given a milestone!". ;-)

We could tweak the system endlessly but I think efforts are best placed 
in working on tickets. I think the system works fine but we could work 
on changing people's expectations that every ticket marked for a 
particular release will magically get fixed by that release.


http://www.freecharity.org.uk/ - Free IT services for charities
http://www.freecharity.org.uk/wiki/ - The VCSWiki

More information about the wp-hackers mailing list