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

Chris Johnston chris at chrisjohnston.org
Mon Mar 10 17:19:11 GMT 2008

Nope.. Just an easier way to differentiate until there is a milestone.. I'd rather look through say 50 defects, 100 enhancements, and 100 of something else than 250 to pick things out.


-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Jared Bangs
Sent: Monday, March 10, 2008 1:14 PM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Probably best to move tickets to 2.7 instead

On Mon, Mar 10, 2008 at 10:00 AM, Chris Johnston <chris at chrisjohnston.org>

> >> I doubt that would be the case. I suspect that as people actually
> worked on
> the tickets they would assign a milestone to them, so you would probably
> have a much more accurate picture of what was actually going to be
> included
> in a milestone release than we have now.
> That's exactly what I'm saying.

Oh, OK. I thought you were talking about assigning non-version based
milestones to tickets for sorting purposes and later changing them to a
version based milestone when appropriate. I was just saying I'd rather have
no milestone specified until there's a real one.
wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list