Ryan Boren

Updates from Ryan Boren Toggle Comment Threads | Keyboard Shortcuts

Ryan Boren 7:48 pm on February 9, 2012 Permalink
Tags: team-update ( 28 )
Team Update: Gardening
- 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 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 ticket target. Suggestions?
Ryan Boren and Joost de Valk are discussing. Toggle Comments
- Joost de Valk 8:03 pm on February 9, 2012 Permalink | Log in to Reply
  
  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 Permalink | Log in to Reply
    
    Such as #18548? Jane’s suggestion of allowing a user specified format is appealing, but I wonder what that would look like in the UI 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 Permalink | Log in to Reply
  
  #14069, #18465 (which needs a redo) #18660, #17977 & #18672 come to mind
  - Ryan Boren 7:06 pm on February 13, 2012 Permalink | Log in to Reply
    
    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.
Ryan Boren 9:21 pm on February 3, 2012 Permalink
Tags: team-update ( 28 )
Team Gardening Update
Decided to allow small schema changes in this release so as to clear out some of the schema updates we’ve long considered.
- #19935 – Drop comment_approved index. It has been redundant for a long time.
- #17188 – Remove blog_id column from wp_options. It has never been used.
We’re also considering:
- #19387 post_content_filtered should be longtext
- #10483 – Change post_name’s length from 200 to 400
kurtpayne modified the ajax handlers to use wp_die() — allowing unit tests to provide a custom die handler — and added more ajax unit tests. #15327

duck_ continued with rewrite improvements: #19876 #16092

scribu continued with work on WP_Query performance in #18536. The results look promising.

And there was the usual trac gardening, unit testing, and housekeeping.
Ryan Boren 6:24 pm on January 28, 2012 Permalink
Tags: team-update ( 28 )
Team Update: Gardening

“Focused” on security, performance, and cache improvements with particular attention to i18n, rewrite, and query. We’re writing lots of unit tests as we go.
- Worked with the lang pack team on splitting up the pot files and loading only the necessary strings for frontend, admin, and network admin page loads. This greatly reduces the number of strings loaded for front page loads, yielding better performance. #19852
- duck_ is improving rewrite. This includes adding API, unit tests, and phpdoc and speeding up performance. #19897 #19871 #16092 #19876 #19875 #19636 and others
- scribu is looking at WP_Query performance #18536
- Hunting down cache bugs such as #19690
- Security hardening such as #19797
- Improved cron locking: fewer race conditions, better performance on busy sites #19700
- Various cleanup, refactoring, warning removal. #16302 r19684 #19249 #15327 #19552 #12307
- General gardening. Mining trac for gold, clearing old tickets that are already fixed or have become irrelevant, triage, etc.
michelwppi is discussing. Toggle Comments
- michelwppi 9:05 am on January 30, 2012 Permalink | Log in to Reply
  
  The splitting of pot files (and in correlation of domains for front and back end) is a very good thing. As developer since 4 years of multilingual plugin (xili-language)… it will able to reduce some api – comment form, wp_locale and other where backend domain is used by core code for frontend (theme domain) – for more details, contact me…
Ryan Boren 10:17 pm on October 17, 2011 Permalink
Tags: 3.3 ( 31 ), beta ( 8 )
Activity since beta 1:
- The blue theme is looking much better thanks to @ocean90.
- @azaozz fixed IE7 and RTL support.
- Flyout menu styling is more spiffy and less glitchy.
- Pointers are pretty much done thanks to @dkoopersmith.
- WP_Screen and contextual help improvements from @nacin.
- Various bug and styling fixes from everyone.
- The “blog front menu” in the admin bar returned to a small snack menu from the full menu we trialed in beta 1.
- Bug scrubs started up again today to finish cleaning up the 3.3 milestone.
- Almost 50 commits since beta 1.
Fabrizio Pivari and Jane Wells are discussing. Toggle Comments
- Jane Wells 11:36 pm on October 17, 2011 Permalink | Log in to Reply
  
  We released beta 1 a week ago, and normally do a new beta after a week. @ryan: Think we’ll be good to do a beta 2 tomorrow?
- Fabrizio Pivari 6:28 am on October 20, 2011 Permalink | Log in to Reply
  
  Where can I find the blue theme in the 3.3 beta 2?
  
  Fabrizio
Ryan Boren 5:32 pm on October 5, 2011 Permalink
Tags: 3.3 ( 31 ), status
We’re getting 3.3 ready for beta. Here’s the gist of how things stand:
- We’re doing daily (almost) bug scrubs in #wordpress-dev to drive down the ticket count.
- Nacin is finishing up WP_Screen and the media button merge.
- Koopersmith is finishing up tabbed help and flyout menu styling.
- Pointers need some styling fixes to be called done enough for 3.3. Pointers will probably be for core only use in 3.3.
- Admin bar needs final walk through and tweaks.
- Welcome box and about this version page need final feedback and tweaks.
- Some of the responsive admin work will be pushed to 3.4 so we have more time to get large screens looking the way we want. Ozz and Jaquith are on it.
- Jane will check all UI/UX feedback tickets and leave comments.
- All task (blessed) tickets should be updated with a comment on current status by the end of the day.
- I will stroke my beard in a diabolical manner while everyone else works.
- Okay, besides that I will be scrubbing bugs, working on more unit tests, and getting coffee for the JS guys.
Bjørn Johansen, Ramoonus, Jane Wells, and 6 others are discussing. Toggle Comments
- donnacha of WordSkill 6:37 pm on October 5, 2011 Permalink | Log in to Reply
  
  Will you be able to get all the diabolical beard stroking into 3.3 or will some of it have to be pushed to 3.4?
  - Ryan Boren 8:16 pm on October 5, 2011 Permalink | Log in to Reply
    
    Diabolical beard stroking is a process, not an event.
    - Bjørn Johansen 1:11 pm on October 13, 2011 Permalink | Log in to Reply
      
      So until PHP gets thread handling this will block all other processing? Could we at least make it a short process and exectute it once in a while on appropriate places with hooks?
  - Andrew Nacin 8:31 pm on October 5, 2011 Permalink | Log in to Reply
    
    Keyword ongoing-project added.
    - Aaron Jorbin 2:57 am on October 6, 2011 Permalink | Log in to Reply
      
      This is why we need to be able to like comments in p2
- Jane Wells 7:00 pm on October 5, 2011 Permalink | Log in to Reply
  
  Updated the 3.3 schedule page to reflect revised target date for Beta 1 to be Oct 7 (Friday, two days later than expected but too bad).
  - Ramoonus 3:07 pm on October 8, 2011 Permalink | Log in to Reply
    
    delay?
- Daniel 9:20 pm on October 6, 2011 Permalink | Log in to Reply
  
  What about tickets assigned to Awaiting Review milestone? At first I thought it was a good idea, but now it looks like Future Release milestone (846 tickets in AR milestone, 1686 in FR). It will be good to quickly review all these tickets and decide which ones can go to 3.3. In 3.4 we either need to conduct a weekly scrub meetings to review all new tickets, or completely get rid of this milestone and let everyone edit the milestone field (or assign next major release by default if you do not want to let anyone to edit it).
  - Andrew Nacin 9:35 pm on October 6, 2011 Permalink | Log in to Reply
    
    Then the issue becomes us punting everything to Future when we’re ready to go to beta, and they further rot. It’s a mess. Locking down the milestones did help. It keeps scope manageable, allows trusted core contributors to make decisions. There are a number of non-committers who have access to these fields.
    
    Yes, sometimes, some tickets fall through. There will always be bugs. But certainly not many get flat-out missed.
    
    You’re right, both buckets need a serious cleaning. We should probably do this systematically after we hit RC and branch 3.3 off. Then trunk can become early development and we can scrub in the month of December.
    
    If anyone sees anything in Awaiting Review now that needs 3.3 attention (non-enhancements), feel free to leave a comment to that effect, and someone will promote it.
    - John Levandowski 2:44 am on October 7, 2011 Permalink | Log in to Reply
      
      I have 2 tickets that I created with patches that I’d like to see included in 3.3:
      http://core.trac.wordpress.org/ticket/18649
      http://core.trac.wordpress.org/ticket/18650
- Jane Wells 12:25 pm on October 7, 2011 Permalink | Log in to Reply
  Have left UI feedback on:
  I’ll circle back on these in the next batch because I have to go load a moving truck at my mom’s:
  @azaozz: Can you pop in on these?
  @dkoopersmith: You’re up.
  - http://core.trac.wordpress.org/ticket/18809
  - http://core.trac.wordpress.org/ticket/11651
  @developersmind: What up, dawg?
  - http://core.trac.wordpress.org/ticket/18295
  - http://core.trac.wordpress.org/ticket/17545
  @nacin: Please hit these or remove yourself as owner so someone else won’t feel like they’re stepping on your toes:
Ryan Boren 3:16 am on May 7, 2011 Permalink
Tags: 32compat, jQuery ( 9 )

Just a heads up. WP trunk uses jQuery 1.5.2. 1.5.2 no longer allows selectors of the form [property=value]. These selectors now require quotes: [property="value"]. Unquoted values will result in “uncaught exception: Syntax error, unrecognized expression: [property=value]“. Check your plugins against 1.5.2.

Andrew Ozz, Around the web | alexking.org, Alex M., and 3 others are discussing. Toggle Comments
- Gary 8:06 am on May 7, 2011 Permalink | Log in to Reply
  
  Now that jQuery 1.6 is released, is that likely to make it in to 3.2 or has it missed the cut?
  
  1.6 does make some changes that might break compatibility – see the release notes about attr() and prop().
- Denis 10:23 am on May 7, 2011 Permalink | Log in to Reply
  
  jQuery 1.6 was released a few days ago, too:
  
  http://blog.jquery.com/2011/05/03/jquery-16-released/
  - Ramoonus 10:53 am on May 7, 2011 Permalink | Log in to Reply
    
    patch #17311
  - Alex M. 12:26 am on May 8, 2011 Permalink | Log in to Reply
    
    It won’t be going into 3.2 in all likelihood though because it will require more robust testing.
    - Alex M. 7:08 am on May 8, 2011 Permalink | Log in to Reply
      
      Or maybe it will…
  - Andrew Ozz 3:43 pm on May 11, 2011 Permalink | Log in to Reply
    
    jQuery 1.6 has some features that would require rewriting most of the code that uses it (thinking mostly about all the plugins that use jQuery). 1.6.1 fixes that and is currently in RC. Hopefully it will be released in time for inclusion in WordPress 3.2.
    
    Oh, and 1.6 still has the same requirement like 1.5.2, all [property=value] selectors have to be fixed.
Ryan Boren 7:24 pm on April 26, 2011 Permalink
Tags: twentyeleven ( 2 )

Ian Stewart (iandstewart) and Lance Willett (lancewillett) will be driving Twenty Eleven theme development during 3.2. You’ll be seeing commits from them for the remainder of the 3.2 cycle as they get our new default theme into shape. Follow the action and provide feedback on ticket 17198.

Joen A., Ryan McCue, and Lance Willett are discussing. Toggle Comments
- Lance Willett 3:03 am on April 27, 2011 Permalink | Log in to Reply
  
  MOAR DEFOLT THEMZ PLZ.
  - Ryan McCue 8:54 am on April 27, 2011 Permalink | Log in to Reply
    
    I’d really like to see a Like button for comments.
    - Joen A. 9:11 am on April 28, 2011 Permalink | Log in to Reply
      
      +1
Ryan Boren 8:47 pm on March 21, 2011 Permalink
Tags: 3.2 ( 8 )

Bug gardeners, there is now a 3.2 milestone in core.trac. Tickets assigned to this milestone should relate to the 3.2 plan. There are currently 312 tickets marked as 3.2 early. Only a fraction of these should end up on the 3.2 milestone.

Mark Jaquith and Rami are discussing. Toggle Comments
- Rami 12:54 am on March 22, 2011 Permalink | Log in to Reply
  
  fraction?
  - Mark Jaquith 4:00 am on March 22, 2011 Permalink | Log in to Reply
    
    A very small amount. Much less than a quarter of them, for instance.
Ryan Boren 3:47 pm on October 14, 2010 Permalink
Tags: 3.1 ( 3 )
Feature status:
- Post Formats landed. Discussing whether to do a core UI in 3.1 that themes can optionally enable.
- Theme Search/Filter is still sitting in rough first draft. Someone volunteered to finish it in the dev chat, but I forget who.
- Internal linking. Daryl has a patch that will go in soon.
- Admin Bar. The first round is in and filosofo is working on a cleanup.
- Ajaxified Admin. Been in for awhile with scribu addressing bugs as they come up.
- Update TinyMCE. azaozz updated to the latest.
- Multi-Taxonomy Queries. First rounds are in and scribu is handling bugs.
- Custom Post Type Index Pages. Nacin landed the first round.
- Cleanup Admin CSS. JohnONolan is working on a first pass.
- QuickPress Function. First round is in.
- User Admin. First round is in along with removal of dashboard_blog.
- Network Admin. Continued bug fixing. Considering moving theme/plugin/core updates to network admin for multisite installs.
New Link Management Now in WordPress Trunk « tekArtist, Arlen Beiler, Tapeleg, and 4 others are discussing. Toggle Comments
- Jane Wells 4:03 pm on October 14, 2010 Permalink | Log in to Reply
  
  Based on John’s update from this week’s UI chat, the CSS cleanup is going to span two releases, as it was a bigger job than anticipated. He’s been working with nacin to make sure nothing will be messed up by what he’s doing.
- Banago 4:47 pm on October 14, 2010 Permalink | Log in to Reply
  
  Lot’s of goodies to look forward to
- filosofo 6:02 pm on October 14, 2010 Permalink | Log in to Reply
  
  I probably won’t be able to make the chat today, but I want to confirm that I’m working on the admin bar changes and will have a patch up this weekend.
- voidmind 12:31 pm on October 15, 2010 Permalink | Log in to Reply
  
  It was not clear where I should send feedback about the site so I’m posting here. The Showcase part of the site doesn’t display images in FF 3.6.10 (Win7) because of an SSL certificate error.
  http://wordpress.org/showcase/
- Tapeleg 2:58 pm on October 16, 2010 Permalink | Log in to Reply
  
  I may have missed it, but is there a fix for changing a site to multisite using subdirectories if the site has been in existence for more than a month? As descried here:
  
  http://codex.wordpress.org/Create_A_Network
- Arlen Beiler 11:50 am on October 19, 2010 Permalink | Log in to Reply
  
  Sounds exciting! Especially looking forward to the Admin Bar and Ajaxified Admin.
Ryan Boren 3:29 pm on August 30, 2010 Permalink
Tags: 31compat ( 9 )

Don’t use the conditional query tags (is_page, is_post(), is_*) prior to init. In 3.0 and earlier, this merely failed quietly. In 3.1 this will produce a fatal error. We’ll workaround the fatal error prior to the release of 3.1, but in the meantime we’ll leave it to serve as a flag for improper use of the query conditionals. If you see a fatal error of the form “Call to a member function is_*() on a non-object” then a plugin or theme is using that function prior to init. See ticket 14729.

Ryan Hellyer and mikeschinkel are discussing. Toggle Comments
- mikeschinkel 5:26 pm on August 30, 2010 Permalink | Log in to Reply
  
  If they fail, wouldn’t it make sense for them to fail loudly? I guess there’s always WP_DEBUG but how many themers and even plugin devs know about it?
  - Ryan Hellyer 2:27 pm on August 31, 2010 Permalink | Log in to Reply
    
    Does WP_DEBUG pick up on stuff like that anyway? I assumed not – haven’ tested it though.

	newtonsongbird on Suggestions
	Kim Parsell on Core Contributor Handbook
	Lance Willett on We’re getting very close…
	Muhammad Abdi on Core Contributor Handbook
	Maor Chasen on We’re getting very close…

Welcome to Make WordPress Core!

Email Updates

Current Dev Cycle

Weekly Developer Chats

Version 3.6 Teams

Recent comments

Meta

Updates from Ryan Boren Toggle Comment Threads | Keyboard Shortcuts

Ryan Boren 7:48 pm on February 9, 2012 Permalink Tags: team-update ( 28 )

Joost de Valk 8:03 pm on February 9, 2012 Permalink | Log in to Reply

Ryan Boren 10:05 pm on February 9, 2012 Permalink | Log in to Reply

Joost de Valk 8:14 am on February 10, 2012 Permalink | Log in to Reply

Ryan Boren 7:06 pm on February 13, 2012 Permalink | Log in to Reply

Ryan Boren 9:21 pm on February 3, 2012 Permalink Tags: team-update ( 28 )

Ryan Boren 6:24 pm on January 28, 2012 Permalink Tags: team-update ( 28 )

michelwppi 9:05 am on January 30, 2012 Permalink | Log in to Reply

Ryan Boren 10:17 pm on October 17, 2011 Permalink Tags: 3.3 ( 31 ), beta ( 8 )

Jane Wells 11:36 pm on October 17, 2011 Permalink | Log in to Reply

Fabrizio Pivari 6:28 am on October 20, 2011 Permalink | Log in to Reply

Ryan Boren 5:32 pm on October 5, 2011 Permalink Tags: 3.3 ( 31 ), status

donnacha of WordSkill 6:37 pm on October 5, 2011 Permalink | Log in to Reply

Ryan Boren 8:16 pm on October 5, 2011 Permalink | Log in to Reply

Bjørn Johansen 1:11 pm on October 13, 2011 Permalink | Log in to Reply

Andrew Nacin 8:31 pm on October 5, 2011 Permalink | Log in to Reply

Aaron Jorbin 2:57 am on October 6, 2011 Permalink | Log in to Reply

Jane Wells 7:00 pm on October 5, 2011 Permalink | Log in to Reply

Ramoonus 3:07 pm on October 8, 2011 Permalink | Log in to Reply

Daniel 9:20 pm on October 6, 2011 Permalink | Log in to Reply

Andrew Nacin 9:35 pm on October 6, 2011 Permalink | Log in to Reply

John Levandowski 2:44 am on October 7, 2011 Permalink | Log in to Reply

Jane Wells 12:25 pm on October 7, 2011 Permalink | Log in to Reply

Ryan Boren 3:16 am on May 7, 2011 Permalink Tags: 32compat, jQuery ( 9 )

Gary 8:06 am on May 7, 2011 Permalink | Log in to Reply

Denis 10:23 am on May 7, 2011 Permalink | Log in to Reply

Ramoonus 10:53 am on May 7, 2011 Permalink | Log in to Reply

Alex M. 12:26 am on May 8, 2011 Permalink | Log in to Reply

Alex M. 7:08 am on May 8, 2011 Permalink | Log in to Reply

Andrew Ozz 3:43 pm on May 11, 2011 Permalink | Log in to Reply

Ryan Boren 7:24 pm on April 26, 2011 Permalink Tags: twentyeleven ( 2 )

Lance Willett 3:03 am on April 27, 2011 Permalink | Log in to Reply

Ryan McCue 8:54 am on April 27, 2011 Permalink | Log in to Reply

Joen A. 9:11 am on April 28, 2011 Permalink | Log in to Reply

Ryan Boren 8:47 pm on March 21, 2011 Permalink Tags: 3.2 ( 8 )

Rami 12:54 am on March 22, 2011 Permalink | Log in to Reply

Mark Jaquith 4:00 am on March 22, 2011 Permalink | Log in to Reply

Ryan Boren 3:47 pm on October 14, 2010 Permalink Tags: 3.1 ( 3 )

Jane Wells 4:03 pm on October 14, 2010 Permalink | Log in to Reply

Banago 4:47 pm on October 14, 2010 Permalink | Log in to Reply

filosofo 6:02 pm on October 14, 2010 Permalink | Log in to Reply

voidmind 12:31 pm on October 15, 2010 Permalink | Log in to Reply

Tapeleg 2:58 pm on October 16, 2010 Permalink | Log in to Reply

Arlen Beiler 11:50 am on October 19, 2010 Permalink | Log in to Reply

Ryan Boren 3:29 pm on August 30, 2010 Permalink Tags: 31compat ( 9 )

mikeschinkel 5:26 pm on August 30, 2010 Permalink | Log in to Reply

Ryan Hellyer 2:27 pm on August 31, 2010 Permalink | Log in to Reply

Code is Poetry

Ryan Boren 7:48 pm on February 9, 2012 Permalink
Tags: team-update ( 28 )

Ryan Boren 9:21 pm on February 3, 2012 Permalink
Tags: team-update ( 28 )

Ryan Boren 6:24 pm on January 28, 2012 Permalink
Tags: team-update ( 28 )

Ryan Boren 10:17 pm on October 17, 2011 Permalink
Tags: 3.3 ( 31 ), beta ( 8 )

Ryan Boren 5:32 pm on October 5, 2011 Permalink
Tags: 3.3 ( 31 ), status

Ryan Boren 3:16 am on May 7, 2011 Permalink
Tags: 32compat, jQuery ( 9 )

Ryan Boren 7:24 pm on April 26, 2011 Permalink
Tags: twentyeleven ( 2 )

Ryan Boren 8:47 pm on March 21, 2011 Permalink
Tags: 3.2 ( 8 )

Ryan Boren 3:47 pm on October 14, 2010 Permalink
Tags: 3.1 ( 3 )

Ryan Boren 3:29 pm on August 30, 2010 Permalink
Tags: 31compat ( 9 )