Subscribe to this blog and receive notifications of new posts by email.
Join 2,296 other subscribers
Andrew Nacin, Xavier, DD32, and 4 others are discussing. Toggle Comments
Schedule update – are we on schedule or is it dropped?
According to nacin in IRC multiple main features like Multisite, Menu Management and custom tax/post are not on schedule. It should at least discussed on how to deal with that.
We are behind schedule. We’ll discuss the ramifications of that in today’s chat. We said when we made the schedule that if things weren’t done we would amend the schedule. I suggest we push everything back 2 weeks to allow for the menu stuff and other things that are a little behind, and target launch for May 1 instead of mid-April. We could use the remaining week and a half before the new freeze date to hold a week-long patch sprint.
That’s good to know because I would appreciate another one and a half week to offer patches for new features.
Regarding the Core Plugins, I’m traveling tomorrow, but will jump on the chat as soon as I can after I land. Not sure if the names next to the items are just crediting those who suggested it or if you wanted me to bring up my question (i.e. what is the status of the core plugins brought up 2 dev chats ago, but not at the last one) for discussion personally.
Either way, just a heads up that I will probably be a bit late to the chat this week.
Sorry to throw this in at the last minute, But if theres any time, Could any devs present see if they can see anything wrong with http://core.trac.wordpress.org/ticket/12250 or why it shouldnt be done like that?
Are the 404s inconsistent between what the function is_404() returns and what the exact http response code is?
If you look into the related tickets, you’ll find that /[retty/permalink/will/fail/ with a 404, but ?p=5555555555555555 will not. Its the inconsistancies in the 404 process, nothing else.
I won’t be able to attend the chat this week due to an ongoing conflict. Re: Trac gardening I really wanted to just get an idea for the schedule and freeze from the lead developers, and where that leaves us with the enhancements and feature requests in Trac. I’ll leave some more ideas here that someone is welcome to cross-reference in the dev chat.
I’ve created a report, http://core.trac.wordpress.org/report/32, that includes all enhancements and feature requests in <= 3.0. (I've excluded Multisite.) I've also begun to work through them and there are about 190 left. There are some tickets with work in progress by a committer which should continue (though in abridged fashion). There are others that deserve a little committer love over the next few days. Most can be simply punted. I think I can finish an initial pass through the entire report and get my eyes on all of them by the end of tomorrow.
I'm trying to take a systematic yet careful approach here. I think there are some tickets that deserve 3.0 consideration but the self-imposed freeze deadline came before many of these simply got any kind of review, so I'm trying to skip those tickets for now and give them a few more days.
It seems we've been moving media/upload-related tickets to 3.1 as it looks like we'll be overhauling that then, so I'm moving those tickets there. Everything else that gets the punt is going to future release for now.
According to the schedule we’re already feature freeze since days. All should get punted to the next version. Those dates were public long enough and there is need to draw a line.
Out of curiosity, are we indeed past the feature-freeze? Seems to go against the whole “we are not on schedule” and “such and such main features still need work” thing.
I have not seen any “we are not on shedule” post on feb 15th or later here on wpdevel. you have any official information no that?
Hakre, just to answer you, I was basing this on your own 12-minutes-earlier post summing up Nacin’s opinion from IRC: “Multisite, Menu Management and custom tax/post are not on schedule”. Since these features seem to be must-haves for 3.0, I could only assume the whole schedule was to be pushed back at least a little during the dev chat – and hence, the feature-freeze not being en route just yet.
Per the dev chat, we’re pushing everything about two weeks. That should give us enough time to push through a lot of unfinished business, and also go on a bit of a patch sprint next week.
I think WordPress Planet should be discussed in another forum. The weekly dev chat is intended to focus on the current dev cycle’s core development. I know we’ve gone off topic a few times before, but we are behind schedule and need to focus on the code. The WordPress Planet discussion is more appropriate to a forum thread on wordpress.org.
If it’s discussed in the forum, the feedback and requests area, can it be made into a sticky?
← I’ve eliminated STYLE_DEBUG because it …
Meeting Summary for February 18, 2010 Dev Chat →