WordPress.org

Ready to get started?Download WordPress

Make WordPress Core

Welcome to the official blog of the core development team for the WordPress open source project.

Here, we make WordPress core. Follow our progress with general updates, status reports, and the occasional code debate.

We’d love for you to help out.

Looking to file a bug?

It’s easy to create a ticket on our bug tracker.

Want to contribute?

Get started quickly. We have some tickets marked as good first bugs for new contributors. There’s more on our reports page, like patches needing testing.

We also have a detailed handbook for contributors, complete with tutorials.

Weekly meetings

We use IRC for real-time communication. As contributors live all over the world, there are discussions happening at all hours of the day.

We have a project meeting every Wednesday at 21:00 UTC in the #wordpress-dev channel on chat.freenode.net. (Quick start: There’s a web interface.)

You can find meeting agendas on this blog. You’re welcome to join us or listen in.

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Jen Mylo 5:25 pm on March 10, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    GSoC IRC Chats 

    The application period opens today and closes on March 21. Between now and then, we’ll set up a handful of IRC chats starting this Wednesday (We’ll use #wordpress-gsoc so as not to distract from the beta work in -dev, and won’t get too close to the dev chat time-wise) to allow some real-time chatting with potential students about their project ideas.

    All mentors should sign up for at least one time slot so the students will know which chat time will have appropriate mentors in the room. Everyone is welcome to attend these chats, not just mentors.

    I’d like to pick 2 times of day and do the chats on Thursday the 13th, Saturday the 15th, Tuesday the 18th, and Thursday the 20th. 21:00 UTC seems to work well for dev chat, so I’m thinking that could be one of the times, but would like a 2nd time that we could do at least once or twice to make it easier on anyone on Australia/Russia side of the world.

    Mentors: Please leave a comment with which days/times you can be available for chats in IRC. If anyone has an idea for a good 2nd chat time, suggestions welcome.

    Thanks!

     

    • Bryan Petty 6:00 pm on March 10, 2014 Permalink | Log in to Reply

      I’ll be at WC Atlanta, leaving the 13th and back on the 16th. I’m pretty sure I won’t be available for the 13th, but might still be able to fit the 15th in. I can commit to the 18th and/or 20th though.

      An Australian/Russian friendly time is certainly a good idea, since GSoC always seems to actually be hugely popular with colleges in India.

    • Ian Dunn 6:13 pm on March 10, 2014 Permalink | Log in to Reply

      21:00 UTC on the 18th works for me.

      (The 13th and 20th would also work if necessary, but the 18th would be a little better.)

    • Aaron Jorbin 6:25 pm on March 10, 2014 Permalink | Log in to Reply

      13th and 20th work best for me.

      13th – 19:00 UTC till 23:59 UTC work best

      20th – 15:00 UTC til 05:00 the next day UTC works best

      I’m not sure there is a time that is good for Russia, East Coast USA and Australia. 0500 is one idea. It’s only 1am on the US East Coast, while being 4pm in Sydney and 9am in Moscow.

    • George Stephanis 9:17 pm on March 10, 2014 Permalink | Log in to Reply

      Most anytime — I’ll be around. :)

    • Yoav Farhi 8:08 am on March 11, 2014 Permalink | Log in to Reply

      The 18th on 21:00 UTC or earlier.

  • Mike Schroder 8:23 am on March 5, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    Last Week in WordPress Core 

    Howdy! This is Last Week in WordPress Core for the week of February 24—March 2! Lots of activity for the past week, which is great as we head into our last few days of alpha. Please join us for daily triage at 1900 UTC to help work through the remaining enhancements scheduled for 3.9.

    As a quick note, if you work with our tools in ‘develop’, and are receiving a SELF_SIGNED_CERT_IN_CHAIN error, you can resolve it by running npm config set ca="". For details, check out this npm blog post.

    If you want to skim, each section is roughly ordered by an important and/or interesting factor.

    Editor

    • Add the ability to drag and drop files directly onto the editor. Upon drop, the media manager will open, and file will begin to upload. [27343] #19845
    • Throttle scrolling of the main window when the editor is active and is being scrolled with the mouse wheel or a trackpad. [27368]. Expect some major tweaks here, though; see #27013.

    Templating

    • Introduce HTML5 gallery support. When a theme supports HTML5 galleries via add_theme_support( 'html5', 'gallery' ), figure, and figcaption will be used instead of definition list markup. [27302] #26697
    • Add a filter to remove or rename page templates for a theme. This does not yet handle adding page templates. [27297] #13265
    • Move comment-reply.js to the footer. While it can function before the page is loaded, it works by moving the comment form, which is usually toward the bottom of the page. Please report any contraindications on the ticket. [27303] #12641
    • Return 404 when querying author’s posts who is not a member and has no posts on the site. [27290] #20601
    • Make get_adjacent_post() wrap a new WP_Adjacent_Post object that uses WP_Query. [27285] [27286] #26937
    • Add exclude and include arguments to wp_list_authors(). [27274] #9902

    Internals

    • Multisite: Introduce get_site_by_path() and further rewrite the site detection process for multisite. This makes it so that a sunrise plugin could do much of its work by adding filters, if those are even needed. [27359] #27003
    • Database: Use MySQLi for WordPress development versions, regardless of PHP version, to increase testing footprint. There’s also a constant for testing purposes. [27257] [27278] #21663
    • Plugin API: Introduce doing_filter() and doing_action() to identify hooks in progress. You can also use this with to identify a hook that has completed. For more, see [27294] #14994.
    • Formatting: Strip backslashes, not just forward slashes, from untrailingslashit(). trailingslashit() will now remove any forward or backslashes from the end of a string before appending a forward slash. [27344] #22267
    • Date/Time: Allow current_time() to accept a date format string, adding to timestamp and mysql. [27259] #21653
    • Updates: During core upgrade, copy wp-includes/version.php over last, to avoid an installation failing with the new version.php in place. [27336] #25860
    • Rewrite API: Allow rewrite endpoints to specify a query variable name. [27327] #20905
    • Cache API: Revert [27115] and let cache backends handle the stripping of spaces in cache keys as necessary. microtime() returns greater precision than microtime(true). [27300] #27000, #23448, #26903, #14485
    • Query: Add a $default argument to get_query_var() and WP_Query::get(). Helpful when working with endpoints. [27304] #16471
    • Comment Query: Allow user_id to be an array of IDs in WP_Comment_Query. [27258] #27064
    • Users: Make the user arguments for get_edit_profile_url() and get_dashboard_url() optional, defaulting to the current user. [27260] [27265] #16686

    External Libraries

    • Update the Masonry JavaScript library to version 3. [27271] #25351
      • The new script handle is masonry. The old jquery-masonry handle is the official shiv that sits on top of the v3 library to be backwards compatible with v2 usage. While v3 no longer depends on jQuery, a theme or plugin may have been implicitly loading jQuery though Masonry, rather than additionally declaring it as a dependency for themselves.
      • Themes should switch to masonry and declare jQuery as a dependency on their own if they need it.
      • Upgrade guide on Masonry’s site, with the exception that, for core, we continue to include imagesLoaded.
    • Upgrade Plupload to 2.x (2.1.1) [27316] #25663
    • Update the Root Certificate bundle used for SSL communication by WP_HTTP from the latest Mozilla release NSS. [27307] #27017

    Developer Tools

    • Add grunt-patch-wordpress for applying patches directly from Trac. Mapped to grunt patch, which declares usage. Requires npm install to install. [27299] #27023
    • Add JSHint to Travis CI config. [27267] #26446

    For the complete list of commits to trunk, check out the log on Trac. Interested in joining in? Write or test a patch for 3.9.

    Thanks to @adamsilverstein, @andy, @avryl, @bassgang, @bootsz, @chrisscott, @danielbachhuber, @DrewAPicture, @enej, @ericlewis, @ericmann, @ethitter, @evarlese, @garyc40, @GaryJ, @gcorne, @georgestephanis, @GregLone, @helen, @iamfriendly, @Ipstenu, @jackreichert, @jeremyfelt, @johnjamesjacoby, @jorbin, @knutsp, @kovshenin, @kpdesign, @leewillis77, @markjaquith, @mattheu, @mboynes, @mitchoyoshitaka, @mjbanks, @mordauk, @morganestes, @nacin, @nicolealleyinteractivecom, @obenland, @ocean90, @patricknami, @pento, @pross, @rickalee, @salcode, @scribu, @SergeyBiryukov, @shelob9, @siobhyb, @solarissmoke, @xsonic, @stephcook22, @theorboman, @tivnet, @TobiasBg, @willmot, @wonderboymusic, @xknown, and @yoavf for their help this week!

     

  • Andrew Nacin 6:00 pm on March 3, 2014 Permalink | Log in to leave a Comment  

    Daily ticket triage meetings at 1900 UTC this week 

    To help realize the goal of a WordPress 3.9 Beta 1 by week’s end, let’s have daily ticket triage sessions in IRC at 1900 UTC, or 2 p.m. U.S. Eastern time. (This is two hours before our usual weekly meeting.) If you’re able to join, see you in #wordpress-dev in one hour.

    We have 99 enhancement tickets open. They either need to be closed or moved out of 3.9 by the end of the week. Just 20 per day will empty that report.

    Of course, a number of us will be in IRC outside of these times as well, working on the same goal.

     

    • Robert Chapin 3:43 pm on March 4, 2014 Permalink | Log in to Reply

      Can we expect some attention on the early tickets?

    • KirkM 4:28 pm on March 6, 2014 Permalink | Log in to Reply

      Andrew – There appears to be a rather serious problem for theme authors who use the “mce-css”filter” to style TinyMCE using a .php file instead of a .css file. This filter was present in WordPress 3.8.1 as well as previous versions. Unfortunately, the “mce_css” filter has gone missing in builds of WordPress 3.9.

      A ticket has been submitted about this:

      https://core.trac.wordpress.org/ticket/27288

      Just FYI

  • Scott Kingsley Clark 8:43 pm on February 28, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Metadata project meeting notes 

    Our meeting today was a great reboot for us, we had a small handful of people attend, with a few additional folks listening in.

    Meetings

    Going forward, we will now meet every Friday at 19:00 UTC, in #wordpress-core-plugins. We will talk about status of various tasks and make any big decisions necessary during these meetings.

    Teams

    We have split our contributors into teams to help delegate responsibilities in a more formal fashion. As a result, we have two primary teams and a “Lead” that will be responsible for vetting proposals and providing direction. We’re still figuring out the best method of communication between members of each team, but the end solution will be public and available for anyone to join and contribute to the discussions throughout the week between our official Friday meetings.

    Please please please please, if you are interested in contributing, get in touch with me or any of the team leads. We are actively looking for help, so don’t be shy and jump on in.

    API

    The registration, initialization, input sanitization, validation, and saving processes.

    UI

    The markup and styling (CSS/SASS) of the meta boxes and fields that are registered by the API.

    JS

    The JS needed for various field types and potentially what we’ll need for repeatable fields functionality.

    Tom, Justin, Micah, and Devin will be reviewing Backbone implementations they are familiar with to discern any areas we may want to implement it’s usage for potentially covering Repeatable fields.

    API team GoToMeeting

    Mike Schinkel will be running a GoToMeeting to go over his ideas for API direction this upcoming Thursday, March 6th, 2014 19:00 UTC, feel free to contact him or watch the recording later. We’ll post a link in the comments here next week and include it in next week’s meeting notes.

    New GitHub repository

    We have also moved our GitHub repo to a new location and setup teams to the corresponding members listed above. It’s now located in the WordPress Metadata org on GitHub

     

    • adamsilverstein 9:34 pm on February 28, 2014 Permalink | Log in to Reply

      Glad to see this effort revived. I couldn’t make the meeting today, although I would still like to contribute – probably to the JS team. Thanks for re-invigorating the effort!

    • Matt Banks 3:49 pm on March 10, 2014 Permalink | Log in to Reply

      Hey Scott – I’d love to get involved and help out with this! I’d like to help out on the UI team, and possibly JS team, depending on time. I’ll hop onto IRC on Friday for the meeting, or I can ping you on Twitter/elsewhere.

    • Scott Kingsley Clark 4:31 pm on March 10, 2014 Permalink | Log in to Reply

      @mjbanks Sure, sounds good to me! If you have time, hit me up in #wordpress-core-plugins any time this week.

  • samuelsidler 4:40 pm on February 27, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Feature Plugin Chat on March 4 

    As mentioned at this week’s and last week’s meeting, we’re going to be holding a feature plugin chat on March 4 2014 21:00 UTC. If you have an idea for a new feature, this will be a great opportunity to bring it up and find others interested in helping out. In fact, just like we’ve done before, post your feature ideas here.

    Please leave one comment per feature idea with the following information:

    • A brief (one paragraph) overview of your feature plugin proposal.
    • Current plugin status (idea stage, planning stage, under development, existing feature plugin, prior work, etc).
    • A list of those involved or already interested in your feature plugin (including you!)
    • What you’d like help with (scoping, planning, wireframing, development, design, etc).

    This post and the accompanying chat is for posting ideas that you’d be interested in working on. It is not for posting every feature idea you have for WordPress.

    Current feature plugin leads: Please post an update for your plugin here, along with the information above.

    See you all at the chat!

     

    • scotthack 4:52 pm on February 27, 2014 Permalink | Log in to Reply

      I’d like to see a plugin built that will accept an XML file to import custom post types and taxonomies. That way theme authors can just provide an XML file with their themes. Then the end user can use the import file to create custom post types and taxonomies and it would be imported independent of the theme.

      This is in the idea stage. My coding skills are very basic, so I’d be of little to no help in the coding department. It would need to be picked up by a competent programmer to actually see it through. I’m only able to help with testing, feedback, and idea conception.

    • UaMV 5:33 pm on February 27, 2014 Permalink | Log in to Reply

      Extend proper author/contributor support when defining custom post types. Currently, when a CPT is registered with support for ‘author’, the metabox returns a list of users with the author role (even if those users don’t have ‘edit_posts’ capability for the CPT. Even in the standard post editor, the author metabox includes only users with an author role, not necessarily those who can contribute (or have edit_posts capability). I believe this metabox should return any user that has the ‘edit_posts’ capability for the specific post type in which the author metabox is being supported.

      There is currently a plugin, Authors Autocomplete Meta Box, in the repository that extends this functionality.

      Rachel Carden (aka bamadesigner) is the author of this plugin (commissioned by ereleases.com). I have, as of yet, had no contact with her regarding the plugin, but find it of great use on my site with multiple CPTs and multiple custom roles.

      Not sure at the moment how I might assist.

    • Janneke Van Dorpe 6:36 pm on February 27, 2014 Permalink | Log in to Reply

      The Front-end Editor is a plugin that allows posts to be edited on the front-end (so it’s really WYSIWYG) and aims to have all the features available that the back-end editor has.

      It’s currently in development on GitHub and updates a posted weekly on the UI blog.

      I’m the project lead (@avryl) and those who are involved or have shown interest are @azaozz, @brainstormforce, @bravokeyl, @gcorne, @helen, @henrywright, @hugobaeta, @joen‎, @kraftbj, @markjaquith, @melchoyce, @mrahmadawais, @obenland, @protechig‎, @rafaelxt, @rhurling‎, @roundhill, @samuelsidler, @shaunandrews, @tillkruess, @ubernaut, @wholegraindigital and others.

      If you’re interested, take a look on GitHub and join our Skype chat (add jannekevandorpe). The next meeting will be Tuesday, 4 March 2014, 17:00 UTC in #wordpress-ui.

    • Chris Reynolds 12:46 am on February 28, 2014 Permalink | Log in to Reply

      AH-O2 (aka Admin Help) is venturing to reimagine the help system in the WordPress admin.

      It’s currently in development is on GitHub with updates being pushed weekly to the WordPress plugin repository. Updates are posted to the Docs and UI P2s.

      I’m the project lead (@jazzs3quence) and other contributors and folks who’ve been involved one way or another are:
      @brainfork, @trishasalas, @jdgrimes, @ubernaut, @zoerooney, @ninnypants, @mdbitz, @clorith, @nikv, and @veraxus

      We need help with:

      1. Documentation — new tooltips are being added to every admin page. Coders (the folks adding them) != writers, so many of these need to be (or will need to be) reviewed, fixed, updated or written. Also, it’s been pointed out that the help overviews we’re building — which replace the help tabs — may not be best suited for the existing documentation in the help tab (which we’re currently pulling from). So help documentation for those areas may need to be edited/changed/added/removed/etc.
      2. Coders — tooltips are added with javascript (and a little php, just to add the translatable string) but fear not! It’s really easy and repetitive. With about 10 minutes of guidance I think I can walk just about anyone through the process of adding a tooltip.
      3. Testers — please break our stuff (and create tickets)! https://github.com/jazzsequence/WordPress-Admin-Help/issues
      Also, extra brownie points to anyone who can test existing, open tickets to confirm/deny a behvior that has an open ticket.

      We meet weekly in #wordpress-sfd on Monday 18:30UTC.

    • Greg Ross 7:50 pm on March 4, 2014 Permalink | Log in to Reply

      The Admin Theme Experience is an update to the existing admin theme system to try and match the site theme user interface. It has two primary goals; simplify the creation of admin color themes and bring the Site Theme Experience to admin themes.

      Current plugin status: under development

      A list of those involved or already interested in your feature plugin: Me!

      What you’d like help with: Anyone with knowledge of the current site theme code would be helpful.

  • Scott Kingsley Clark 9:50 pm on February 25, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Metadata project update 

    Greetings all! I’m Scott, I’ve been involved as the secondary lead on the project, with primary co-lead Eric Andrew Lewis (@ericlewis). As of today, Eric and I have switched roles. Eric’s time has had a few schedule conflicts pop up, but he’ll still be participating.

    Next Meeting

    We haven’t posted any updates here since January, but I aim to get us back track, starting with a meeting this Friday, February 28th, 2014 19:00 UTC to reboot contributor involvement.

    If you’re interested in joining us and contributing help, please join us, we’ll help assign people tasks and areas to participate.

    Donating dev time to core

    My employer, WebDevStudios, has graciously donated a block of time each week that will be devoted to me working on this project. I’m excited to be more involved and active on a core project. I’ll also be following trac tickets for the Options/Meta component on Trac to help out where I can there. I encourage others to also step up if this project is one your company or team has a vested interest in.

    More info

    If you’d like more information about the Metadata project currently in progress, check out our previous blog posts.

    Also check out the cool dashboard for the Options/Meta API component!

     

  • John Blackbourn 9:58 am on February 25, 2014 Permalink | Log in to leave a Comment
    Tags:   

    Contributors Wanted for WP Contributor Day, Manchester, UK 

    WP Contributor Day is a free, one day event focused on enabling and demystifying how everyone can contribute to core. The first event is this coming Saturday – 1st March.

    The organiser, Jenny Wong, is looking for existing contributors to come along and help guide the new contributors.

    From the poll of people who have already signed up, it would be great to have a couple of people from core, themes, plugins, documentation, support and accessibility come to Manchester for the day. Those are the current most popular areas.

    More information can be found at wpcontributorday.com.

    If anyone wants to contact Jenny, she can be found on Twitter at miss_jwo or via email at wpcd@jwong.co.uk.

     

  • Mike Schroder 8:01 am on February 25, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    Last Week in WordPress Core 

    Howdy! This is Last Week in WordPress Core for the week of February 17th-February 23rd. A few commits to highlight this week, but before we get to that, a quick update from the trac sprint last friday.

    Friday Trac Sprint

    Thanks to everyone who participated! Great progress was made during the trac sprint last friday, triaging and replying to the tickets that need a response. Working together, we brought the number of tickets down by 200! But, we’re not done yet! Minus the 50 tickets created by committers/gardners, there are 191 left. If you’re interested in helping out, check out @nacin‘s notes on providing feedback. As always, feel free to ask for help in #wordpress-dev if you run into any questions.

    Internals & Backbone.js

    • Added support for ext/mysqli, which will be used by default in PHP 5.5 or greater. Please test this, as it’s quite possible it will cause issues. r27250 #21663
    • Updated Backbone.js to version 1.1.2. r27233 #27182
    • Added an abstraction for groups of media in media-editor.js called wp.media.collection and refactored galleries to use them. r27212 r27213 r27214 r27215 r27238 #26631
    • Added boolean return values to require_if_theme_supports(). r27217 #26716
    • Declared and documented $wpdb->base_prefix. r27249 #16762

    Media

    • First pass of a/v playlist support. Please test, and note on the bug if you notice anything amiss! A few details from the commits: ( r27239 r27242 r27243 r27244 r27245 #26631 )
      • Playlists operate like galleries in the admin.
      • Provides default UI and JS support in themes using MediaElement and Backbone.
      • The shortcodes are clickable, editable, and configurable using the media modal.
      • Playlists support images for each item, whether or not the current theme supports images for attachment:audio and attachment:video
      • Playlists respond to $content_width and resize videos accordingly.
      • All playlist data is included inline, using a script tag with type="application/json", allowing anyone to unenqueue the WP playlist JS and roll their own.
      • Playlist styles are minimal and work out of the box in the last 5 default themes. They inherit and adapt to the current theme’s font styles, and their rules are easily overrideable.

    Dev/Build Tools

    For the complete list of commits to trunk, check out the log on Trac. Want to help out this week? Write or test a patch for 3.9.

    Thanks to aaroncampbell, avryl, azaozz, bcworkz, brasofilo, corvannoorloos, danielbachhuber, dougwollison, DrewAPicture, ericlewis, gcorne, helen, ipstenu, jeffsebring, jorbin, juliobox, kovshenin, kpdesign, MattyRob, meloniq, nacin, netweb, ocean90, OriginalEXE, pento, scribu, SergeyBiryukov, shelob9, theorboman, TobiasBg, wonderboymusic, and everyone who helped out with the ticket triage last Friday for their efforts this week!

     

  • Jen Mylo 7:00 pm on February 24, 2014 Permalink | Log in to leave a Comment
    Tags: ,   

    We’ve been accepted as a mentoring organization for GSoC! Now comes the work of interacting with potential students on wp-hackers (let’s try to be responsive, and nice) and in #wordpress-dev and #wordpress-gsoc (I’ll set up a few scheduled chats soon, but idle in the channel if you can to field questions) during the application period. Mentors, I’ll contact you within the next couple of days to set up chat times and discuss the application review process.

    Thanks to everyone who helped get our Ideas page filled!

     

  • Andrew Nacin 11:29 pm on February 20, 2014 Permalink | Log in to leave a Comment  

    Friday Trac Sprint 

    I mentioned this in the dev chat on Wednesday: Join us tomorrow (Friday, February 21) for a sprint through Trac tickets that need a reply!

    A few weeks ago I said one goal of mine for the 3.9 cycle was to make contributing easier and more accessible. That’s why so much work has gone into improving our tools in the last few months. One task is to empty one particular report of tickets: tickets that need a response. After that, I’d like to keep it empty.

    As of this writing, there are 386 tickets on this report. (The report shows 441, as that includes another 55 opened by a committer.) Help us empty this report!

    To best coordinate a few dozen people all trying to comment on a few hundred tickets, please join us in #wordpress-dev in IRC. We’ll break these tickets into chunks, such as by age, component, or focus.

    We’ll have people in IRC all day to help you out if you haven’t triaged tickets or given feedback before. There is a whole set of guidelines in the comments below. @SergeyBiryukov and @ocean90 will be around for morning in Europe, and I’ll be around starting at around 9 a.m. U.S. Eastern.

     

    • Andrew Nacin 7:53 am on February 21, 2014 Permalink | Log in to Reply

      The main goals here are to make sure that tickets and patches have received some form of initial feedback. That’s just the first step in a long process, of course, but it’s an important one. If you’re new to this, here’s some tips on how you might approach and handle a ticket:

      When giving feedback for a ticket:

      • Thank the individual for the report. Some of these tickets are quite old; for those, a simple “Thanks for the report nacin. Sorry you never got a response.” is fine.
      • If this was one of the reporter’s first tickets, it will tell you above the comment box. Be nice. :-)
      • If it’s a support request, you can refer them to the WordPress.org support forums and close the ticket as “invalid”.
      • If it’s a bug report that sounds like an enhancement, then change the ticket to an enhancement. Enhancements are a bit more difficult to triage (as the feedback is more subjective), so it’s much easier to start with bugs.
      • Consider a quick search to see if it is a duplicate of another ticket that may be farther along.
      • If there’s a component that is more appropriate for the ticket, feel free to move it.

      If it’s a bug report:

      • See if you can still reproduce it in trunk. (And/or try 3.8.1.) Some bug reports may have been invalid to begin with; others might have been fixed already.
      • If when reproducing it, you feel you can elaborate on the issue, or write clearer steps to reproduce, please do so.
      • If you can’t reproduce it, ask the reporter for more information and add the “reporter-feedback” keyword. If you think the ticket should be closed, you can mark it with the “close” keyword. (There doesn’t need to be a rush to close the ticket.)

      If it has a patch:

      • Test it out — does it fix the problem? How did you test it? Did you notice any side effects?
      • If the patch doesn’t apply cleanly (as in, it fails when you try), add the “needs-refresh” keyword.
      • If you’re a developer, consider doing even just a cursory code review.
      • If the “has-patch” workflow keyword is missing, add it. Or, if after review you don’t find the patch to be sufficient, you can set it to “needs-patch” instead.
      • If you feel the patch is ready to be reviewed by a core developer to be considered for inclusion in WordPress, simply say so.

      It might take only a few minutes to triage some of the more straightforward tickets, especially once you get the hang of it. You could easily spend twenty or thirty minutes on others, or even longer if there’s a lot to test or if you have a lot of feedback to give. Take your time; the post calls this a “sprint” but it’s not a race!

      If you come across a ticket you like and want to write a patch for it, that’s great! Feel free to leave feedback on the ticket and start working on a patch. If you end up working on just that for today, that’s totally fine — there are a lot of others working through this list of tickets, too. Triaging can be a great way to find tickets that interest you.

      A number of us will be in #wordpress-dev to help you out. So people don’t overlap, we’ll try to point you to a particular collection of tickets, based on your interests. If you’re unsure what to do for a particular ticket, feel free to move on. Or even better: Ask in IRC and we can talk through it.

      (If you are craving even more detail on triaging tickets, the contributor handbook has a whole page on bug gardening.)

← Older posts

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel