[wp-hackers] Decision time in re: admin rework

[spencerp]

Viper007Bond wrote:
> The whole point of the timelines was to nudge us along and get releases out.
> By not having a set date, we risk dragging on forever.
>   

Oh yeah, I know... =D I guess with this "one" (2.4), with all that was 
planned to get in "it" and then also having those 500 some tickets 
there, that were originally planned for two to four versions 
previously... Kinda makes one feel like... "Crap, all this stuff... so 
little time, oh well.. if we don't get it all in this time, maybe the 
next time eh?"

Next time rolls around.. instead of having 500 some tickets, there's 600 
to 700 with even more better stuff planned to get in the next version 
(2.5) ... then cycle repeats again for 2.6.. or whatever... Basically 
was just saying... maybe (if need be)... take a version and get what you 
can get done with it, and not really worry too much if it goes over the 
"expected release date" for some catching up...

I mean, don't do this all the time... but maybe some times, to help cut 
down on the backlog in Trac and or whatever else that comes up later 
down the road for "new features" that were voted to go into core... So 
"we're" not always getting behind... Take some time through version 
releases to catch up too. Not just slap more into core, while leaving 
more slug trail goop behind at same time..

> On 12/20/07, spencerp <spencerp1 at gmail.com> wrote:
>   
>> Matt Mullenweg wrote:
>>     
>>> Doug Stewart wrote:
>>>       
>>>> As we all know, the end of 2007 is rapidly approaching, with January
>>>> 24th right behind.  With just a hair more than a month to go, does it
>>>> still make sense to pursue the admin rework/Happy Cog contributions as
>>>> a 2.4 goal?
>>>>         
>>> Thanks for your opinion. I'm going to make a decision about this over
>>> the holidays and will let wp-hackers know.
>>>       
>> I know you're on a time frame release schedule, but like someone else
>> said on wp-testers... Why not just do what you have to do to get it in
>> there or whatever, and release when it's "ready"? Does it have to be
>> released Jan 24th? *ducks under table quick *
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>>     
>
>
>
>