Team Update: Gardening

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

duck_ finished the rewrite tickets that were in our sights and moved on to import/export.
The WP_Query improvements might land soon (#18536). I want to do some more testing with memcached first.
The ajax code reorg is done (#15327). A few variable scope related bugs were fixed. Unit tests added.
post_content_filtered is now the same size as post_content (#19387). Rejoice. I think this concludes the schema changes for 3.4.
Review, test, commit, and pinch hit for other teams.
Profiling of various adminadmin (and super admin) pages, looking for slow things.
And the usual gardening activities. The winnowing is slow but steady.

Coming up:

Land WP_Query changes
Import/export
More unit tests
Particularly autop unit tests. Anyone?
Pick a couple of new components to ticketticket Created for both bug reports and feature development on the bug tracker. target. Suggestions?

#team-update

Joost de Valk 8:03 pm on February 9, 2012

There are quite a few tickets with patches that have been checked related to SEO; canonical, robots headers, titles, those stand a chance?
- Ryan Boren 10:05 pm on February 9, 2012
  
  Such as #18548? Jane’s suggestion of allowing a user specified format is appealing, but I wonder what that would look like in the UIUI User interface when all is said and done given the number of conditionals the title code handles. I’d love to see someone run with this. It might not make it into a gardening cycle or 3.4, but it is something we definitely want soon.
  
  Beyond #18548, I can see a cycle for those other things. duck_ and nacin have already done a fair bit with canonical and 404, we can make an official cycle out of further fixes. Particular tickets in mind?
Joost de Valk 8:14 am on February 10, 2012

#14069, #18465 (which needs a redo) #18660, #17977 & #18672 come to mind 🙂
- Ryan Boren 7:06 pm on February 13, 2012
  
  I could go for #18645 and #18660. And cleaning up kses allowed tags handling to make things like #17977 easier is something nacin and I have been talking about.

Comments are closed.

Welcome!

Communication

Share this: