Wound up realizing we’ll be thanking all the core contributors on the dev blog in the release announcement in a couple of weeks, so decided not to do it for thanksgiving and wind up with duplicate content. Did a post thanking forum volunteers today, though, and linked to a thread in forums to hold discussion around ways to make volunteering easier. Am thinking a couple of weeks of discussion while we’re trying to get 2.9 out the door followed by a holiday break to consider ideas would be a good precursor to launching some new community stuff early in 2010.
Updates from November, 2009 Toggle Comment Threads | Keyboard Shortcuts
-
Jane Wells
-
Peter Westwood
Next dev chat will be on Thursday 3rd December at the usual time of 9PM UTC. This weeks is skipped due to Thanksgiving.
Please leave Agenda items on the post below: http://wpdevel.wordpress.com/2009/11/19/suggest-agenda-items-for-nov-26th-dev-ch/[Lloyd edit: I'm guessing that westi has closed this thread for discussion because comments should be posted continuing the previous discussion -- "Please leave Agenda items on the post below: http://wpdevel.wordpress.com/2009/11/19/suggest-agenda-items-for-nov-26th-dev-ch/ "]
-
Jane Wells
In light of Thanksgiving, I’m going to do a “thanks” post for the dev blog this week since there’s no dev chat. Thinking I’ll call out the people who’ve contributed a patch (committed) to core since 2.7 (this year, basically) and forum moderators (and forum participants who do a solid job of helping people in the support forums without the official moderator label). Since we all know what a manual and aggravating task it is to make a list of core contributors (we need a better system for this), people can use this post to leave comments to give props to people who go above and beyond helping users in the forums, and if you’ve had a patch committed this year, maybe check your Trac profile to see if you have an actual name and/or URL listed in your profile. Thanks.
-
demetris
Jane:
http://op111.net/misc/wp-29-props
It is to be used by whomever writes the release announcement for v2.9.
(This is a temporary page, not visible in the website navigation, and I am not going to publish it properly. I’m just maintaining the list, so that it will be ready for the release announcement. Oh, and people can also edit the source, or just send me a message, if they have any corrections or additions.)
-
Jane Wells
@Demetris: How are you compiling this list? By hand or do you have a handy script around that is pulling from the props lines?
-
demetris
By hand.
But it didn’t take take that long. (With a browser that supports relational links and also keyboard shortcuts for relational links, so that I did not have to take my hands off the keyboard.)
-
-
Denis de Bernardy
Why is this still typical?
-
Jane Wells
5 months with no community activity does not a high priority ticket make.
-
Denis de Bernardy
It removes nothing to the fact that there is a serious problem and that I’m not the only one who thinks there is:
-
Peter Westwood
Please keep discussion about ticket counts and progress off of tickets.
It does nothing but create extra noise.
-
-
-
Denis de Bernardy
seems this needs discussion
-
-
Peter Westwood
-
Peter Westwood
Suggest agenda items for Dec 3rd dev chat
-
Matt Martz
How do we handle security releases in the admin? If a user is running an old 2.8 such as 2.8.1 do we tell the user that 2.8.6 is available or 2.9? And when on 2.8.6 tell them that 2.9 is available? Or do we need to do another release in 2.8 to give us more UI capabilities so that we can tell the user that both 2.8.6 is available and 2.9?
We covered this a little in the Dev chat for the 19th. Everyone think it over and come back with some ideas.
I would like to see us start with 2.8, so we should get this figured out soon.
-
Daryl Koopersmith
We might want to reschedule this week’s dev chat since Thanksgiving is on the 26th for us Americans. Thoughts?
-
Matt Martz
That is a good point. I will actually be travelling and not available for the meeting. I leave Wednesday and am not back until Sunday. I say move the meeting to Tuesday or maybe skip a week.
-
Peter Westwood
I have started a poll above to get some feedback
-
Peter Westwood
Decision is to skip this week and move to the 3rd.
-
-
-
Denis de Bernardy
Re: http://core.trac.wordpress.org/ticket/10738#comment:5
Imo, it is Appearance that should have been renamed back to Themes… I don’t know about others, but that one was one change to the UI that I did NOT find relevant (at all)
-
Peter Westwood
I think this is better discussed on the ticket rather than in the meeting – do you want to comment there.
-
Denis de Bernardy
I’ve opened http://core.trac.wordpress.org/ticket/11224
-
-
Dre Armeda
Denis, I think Appearance is appropriate but there are other items I would like to see added. I commented on the ticket.
-
Jane Wells
Added my comment to trac late, so repeating here. Was renamed Appearance b/c so many people got lost looking for widgets, which regular people don’t associate with themes. We can address possible re-naming in 3.0, when we’ll address menus (with merge) and header/nav touch-ups (postponed from summer).
-
Matt
Good point on Widgets, I had forgotten about that.
-
Denis de Bernardy
The point on docs is much more compelling imo. It’s end of story, even.
-
Lloyd Budd
@Jane > we’ll address menus (with merge) and header/nav touch-ups
Link to more info? Would be good in the tic too. -
Jane Wells
@lloyd > There is no info yet; we aren’t starting to think about the merge until 2.9 is out the door.
-
-
-
Denis de Bernardy
Create a post on the wp.org dev feed that highlights what breaks to plugin devs. And do so with every release.
My own tests didn’t reveal much that broke with 2.9 except for the new trash status. Then again I’m sure I’m missing things since I’ve no plugins that mess around with comments.
Anyway, the point would be to highlight what breaks and why in language that plugin devs can understand. In the case of the new trash can, it means something like:
WordPress’ new Trash feature introduces as new post status, and a new comment status. Contrary to revisions in WP 2.6, which had introduced a new post type, this new “trash” status has the potential to break plugins.
Yours might be broken if it uses direct SQL queries with no constraints on the post or comment status field, such as:
http://core.trac.wordpress.org/changeset/12254
yada, yada…
-
Denis de Bernardy
Adding to the previous comment, there might still be other queries in WP that might need to be looked into.
-
-
-
Jane Wells
Since announcement that Google is ditching Gears, I wonder if we should remove Turbo link from header (and possibly from Tools section of admin as well)?
-
Matt
Tracking here from Ryan:
-
-
Jane Wells
I’ll be out today during dev chat. Have to go buy a car to replace the one that was totaled in my car accident earlier this week. I’ll be in Orlando for WordCamp as of tomorrow, and will catch up with the core guys who will be there to see what I missed.
My votes: punt all edge case bugs/those that haven’t been reproduced/those that only one or two people have commented on if there hasn’t been adequate patch testing; ditch gears link in header; hold off on changing default post text until 3.0 pending some testing; hold off on pretty much any proposed UI changes since there’s not really time to adequately test new stuff now and do the release in December (and we’ll be doing UI touch-ups in 3.0, so waiting until then will have a lower pain level for all the documentation etc). Of note: Ben Dunkle is about done with the new icons for the media editing stuff, so those will make it in before RC.
Also, CodePress is disabled but still in WP, but as I understand it, it’s not being maintained and people have been testing alternatives for inclusion. Should CodePress be removed from 2.9 to trim core, or would pulling it out now cause trouble?
-
demetris
1. A question/reminder: Is the wp-announce list working? Will it be working for the point releases in the 2.9.
2. A proposal to discuss minimum intervals between first beta and final release, and between first RC and final. Mainly for the benefit of plugin/theme devs and of translator teams, and also in order to catch the occasional shy bug.
Say:
At least 4 weeks interval between Beta 1 and Final, and at least 2 weeks between RC 1 and Final. In normal circumstances, the 4 weeks could be allocated evenly somewhat like this:
Beta 1
Beta 2 after 1 week
RC 1 after 1 week
RC 2 after 1 week
Final after 1 weekRC1 could also be a good point for string-freeze.
Denis de Bernardy, 
Peter Westwood
Agenda for Nov 29th Dev Chat
- 2.9 beta status review – mark/ryan/andrew/peter
- Patch backlog – demetris
- Page Templates in subdirs – peter
- WPMU Compatibility – sivel
-
scribu
I suppose that’s Nov. 19th, right?
-
Peter Westwood
Yes.
-
-
Matt Martz
Discuss adding WPMU to the wp.org plugin compatibility box, or perhaps a second box?
Matt
“Relentless attention to detail, a passion for user experience, and a compassion for users.”
Something for us all to aspire to.
-
Kirk M
Congrats on WordPress winning best open source CMS award this year. A fine job by all.
-
Jane Wells
“A passion for user experience”
My mom thought that was awesome. -
Matt
You’re one of them!
-
Mark Jaquith
-
Shane
oh yeah. Time to really kill some bugs.
Ramoonus
release notes?
-
Alex M. (Viper007Bond)
Yeah, anyone know of a list of the major features? I’ve lost track of them all, but I know the highlights are image management, embeds (woot), trash, uh…
-
Dre Armeda
Alex, this what you’re looking for? http://codex.wordpress.org/Version_2.9
-
Alex M. (Viper007Bond)
You mean the Codex contains helpful information about WordPress? What a novel idea!
(In short, duh, why didn’t I think to look there? lol, thanks!
)
-
Ryan
Lol, this broke my site something wicked! I’ve been testing the trunk install for about a month now and am yet to find a single bug!
gillesv
Does the_post_image() work yet? I tried it locally but am seeing nothing?
-
Aaron Brazell
your theme would need to support it with the add_theme_support() function.
-
Alex M. (Viper007Bond)
Example: https://core.trac.wordpress.org/changeset/12133
Although the post images are meant to be used outside of the content area.
Ryan
http://dougal.gunters.org/blog/2009/10/16/wordpress-2-9-features
http://technosailor.com/2009/11/11/10-things-you-need-to-know-about-wordpress-2-9/
-
Matt
Aaron’s has a few things that aren’t actually new.
-
Dre Armeda
Aaron also listed that the PHP5 requirement is coming in 3.0, I thought that wasn’t set in stone?
-
Mark Jaquith
Some things already require PHP 5, like time zone support or oEmbed. There are no plans that I know of to remove PHP 4 support in 3.0 — last I checked we still had 12% of WP installs using PHP 4.
I see more of a natural and gradual deprecation of PHP 4. We’re very much open to making new features require PHP 5 if it would be a pain to make them PHP 4 compatible.
-
Alex M. (Viper007Bond)
To be clear, oEmbed doesn’t require PHP5, it’s just that XML decoding isn’t supported under PHP4 (not worth the trouble). That’s not a big deal though as most sites support JSON and we have a class that provides JSON support for PHP4.
-
Dre Armeda
Mark, that’s what I thought. Just a bit misleading in the post. I also agree that a gradual deprecation of PHP 4 is more likely, eventually it will run its course.
-
Matt
Correct, there are no plans to change the minimum requirements.
-
Aaron Brazell
I will update the post. Mark already corrected me and I acknowledged in comments. Just haven’t had a chance to update.
-
Dre Armeda
Aaron, great post by the way!
-
Ajay
I can’t download it using the plugin
-
Kirk M
If you mean the WP-Beta-Tester plugin I believe that only deals with point release nightlies (currently states it’s a development version of 2.8.6 or that’s what it says when I just checked it on my test site anyway) and bleeding edge nightlies (2.9 rare). I don’t think you can use it to download beta builds or at least I can’t.
-
Alex M. (Viper007Bond)
Beta 1 is just a particular nightly. Once a version of WordPress hits beta, it’s better to run trunk (nightlies) than the above ZIP anyway (it’s more up to date).
-
-
Kirk M
Alex – That’s what I thought although I did want to check it out. Just FYI: I switched the plugin back to “Bleeding edge” and auto upgraded to 2.9 beta 1
Go figure.
Kirk M
Mark – Just to avoid confusion, the “version.php” file in the .zip file for 2.9 beta 1 shows as “2.9 (rare)” and not “2.9 beta 1″. Some testers are being thrown off by this as this. Was this intentional or just something that was missed?
Peter Westwood
Suggest agenda items for Nov 19th dev chat
-
Denis de Bernardy
This here is a valid point:
http://core.trac.wordpress.org/ticket/2699#comment:27
And this would be very sweet for the grand unified upgrader:
-
demetris
I wanted to propose a discussion on how to attack the backlog of tested but uncommitted patches:
http://core.trac.wordpress.org/report/6
… but I see some heavy activity in the last couple of days, which makes me happy. Would it be realistic to set as a target to commit all stuff that has both HAS-PATCH and TESTED before RC1? If yes, what can we do to help?
On the release-notes front, I just finished a list of all contributors that have received props from r11552 (start of 2.9-rare) up to r12218 (committed earlier today), along with full names and links for the most part.
-
Peter Westwood
We should focus on bugs in new features and regressions.
We should not go on a big commit marathon when we have limited tester bandwidth as it will be harder to track down new regressions.
-
demetris
Thanks for the answer!
I’ll make a note to bring this up again after 2.9 final is out.
-
-
-
Peter Westwood
Page Templates in sub directory of theme – http://core.trac.wordpress.org/ticket/10959
-
Dre
Westi, this is not working in 2.8.6 correctly either. I agree the capability should work in parent and child themes if it is to be included.
-
Peter Westwood
Agenda for Nov 12th Meetup
- 2.9 status – Ryan/Andrew/Peter/Mark
- Plugin Compatibility – Aaron
- Minimised css/js – scribu
- FOSDEM developer room – Nikolay
- security functions – Mark Jaquith
-
Weston Ruter
Regarding minimized JavaScript, I’ve been working on a plugin that automatically concatenates scripts and compresses them using Google’s Closure Compiler. Here’s the work in progress: http://gist.github.com/233399
Perhaps scribu has already finished what I’ve been working on, but in any case, I wanted to alert you to my related project.
Matt
I find this page inspiring:
-
demetris
I stumbled upon it recently, while looking into how other projects present their prominent features[1] and credit their upstream code[2], and I agree.
The Mozilla project suffers from some of the same problems as the WP project, like the info-and-docs-all-over-the-place problem, but they have their good moments too.
1. http://codex.wordpress.org/User:Demetris/Features
2. http://codex.wordpress.org/User:Demetris/Credits -
Dre Armeda
Matt,
This is a great way to encourage the community, I think something like this would be a great way to engage.
BTW, great interview last night
-
Dre Armeda
Matt,
This is a great way to encourage the community to get involved, great way to engage! Lets build it
BTW nice interview last night with Jason.
-
Dre Armeda
Demetris,
Let me know if I can offer a hand with the Features page.
Sorry for the triple post here guys.
-
demetris
Thanks, Dre! The more hands and ideas, the better.
For now, I’m not doing any work on the Features page, waiting for some feedback and a decision about it: When are we going to change it and what we want the new page to look like (approximately).
-
-
Dre Armeda 3:50 am on December 1, 2009 Permalink |
Great post Jane
Let me know if there is anything I can help you with.
Cheers,
Dre