[wp-hackers] 2.4/2.5 release

[DD32]

It just means that bugs filed for 2.4 can be pushed to 2.5 when updating the tickets, And anything remaining in the 2.5 milestone come closer to release time get pushed to 2.6.
nothing "has to be" fixed in any release (Allthough idealy most would love for all the tickets to be fixed for each milestone)

On Thu, 03 Jan 2008 11:37:48 +1100, Dave W <dabbaking at gmail.com> wrote:

> So does this mean that all the bugs pushed to 2.5 are going to have to be
> fixed now?
>
> On Jan 2, 2008 7:29 PM, Matt Mullenweg <m at mullenweg.com> wrote:
>
>> In light of the big changes happening in the codebase and admin section,
>> we're going to push back the next release to be aimed for early March.
>>
>> This is the timeframe when 2.5 was originally schedule for, so we're
>> treating the originally planned 2.4 in December as a skipped release, as
>> a result of both the holidays and the large changes which we weren't
>> able to start on until late October.
>>
>> There's some good stuff in the oven, and we don't want to rush it.
>>
>> The new release shall be called 2.5. Various official docs and roadmaps
>> will be updated in due course.
>>
>> --
>> Matt Mullenweg
>>  http://photomatt.net | http://wordpress.org
>> http://automattic.com | http://akismet.com
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>