Start Your Engines…

Posted April 16, 2009 by Jen. Filed under Development.

The 24-hour has-patch marathon has just officially begun! For the next 24 hours (until Friday, 4pm UTC), the core developers will be evaluating patches that have been tested and committing those that are good. When they run out of those, they’ll start testing patches that have been submitted but not tested. This takes longer, so help us keep the momentum going by testing patches today.

Grab yourself a copy of the nightly build to make sure you’re using the right version, then head over to Trac and start looking at the has-patch* tickets. Pick a ticket, download the diff, test it out on the browsers/platforms you have available, and write a comment about the results in the ticket’s comment thread. Move on to the next ticket. Do as many as you can over the next 24 hours.

And if you’ve got the mad skills to contribute bug fixes and code patches for enhancements and other tickets, now is also a great time to contribute a patch. Why wait? One of the complaints I hear in the IRC #wordpress-dev channel is that it can be frustrating to write patches because sometimes it takes a long time for them to be reviewed and committed. For those people (and everyone else), this is the perfect time to patch, because we’ll be looking at every has-patch ticket in Trac for 2.8 over the next 24 hours. If you have a patch that’s been submitted but it hasn’t been tested, consider doing a little PR for yourself. Hop in the dev channel, post on your blog, mention on Twitter that you need people to test your patch *today* so that it can move forward in the process. This will speed things along. You can also add the keyword needs-testing in addition to has-patch.

At the end of the 24-hour period, you don’t have to put your pencils down, but the core devs will be going to sleep and then returning to the regular dev cycle, so it’s worth it to contribute today. If you miss the deadline, it’s okay; you can contribute or test patches as usual, you just won’t get the more immediate gratification the marathon promises.

We’ll post the results of the marathon here on Monday, after everyone’s gotten some rest and we can go through the Trac logs to see how many people got involved. This is one reason it’s so important to leave a comment when testing patches…it’s how we’ll be counting the number of marathon testers. Top patch contributors and testers will be recognized in the results post, so if that sort of thing motivates you, let the link love lead the way.

Of note: we are now in feature freeze for 2.8!

* – For those who don’t know why I keep using the term has-patch… When someone submits a patch by uploading it to the Trac ticket, they add “has-patch” to the keywords field, so that the core devs will know there’s a patch attached. Not the most elegant system, true, and you’d think maybe Trac could just recognize that a certain file type had been uploaded, but there you have it.

No Pings

RSS feed for comments on this post.

  1. […] I knew the patch marathon was going on today, but today also marks the day that WordPress 2.8 is feature frozen! Yippe!! No […]

    Pingback from Feature Frezze in effect on WordPress 2.8 | the rabbit hole on April 17, 2009

  2. […] Before WordPress has a bug hunt, which would result in the addition of dozens of new tickets, they need to work on clearing out some of the old tickets in Track. What a great way to help a open source project. There are lots of ways to contribute, for more information you can check out the original article here. […]

    Pingback from Webbhawk | WordPress 24 hour Has-Patch Marathon on April 17, 2009

  3. […] dem WordPress Entwickler-Blog befindet sich die kommende WordPress-Version WordPress 2.8 im feature freeze. Das heißt, neue […]

    Pingback from WordPress 2.8 Feature Freeze - feature freeze, Funktionen, WordPress, Stattdessen, Fehler, WordPress-Version - WordPress Deutschland Blog on April 18, 2009

  4. […] dem WordPress Entwickler-Blog befindet sich die kommende WordPress-Version WordPress 2.8 im feature freeze. Das heißt, neue […]

    Pingback from WordPress 2.8 Feature Freeze | Der Mediablog on April 18, 2009

  5. […] 在WordPress的在新版本中增加了几十个新的改改动,并清理了一些旧的不常用的部分,原文在此 […]

    Pingback from WordPress资料站 » Blog Archive » WordPress 2.8 Marathon 的开发接近尾声 on April 18, 2009

  6. […] est glissée discrètement en fin de l’article annonçant le début de la chasse aux bugs en 24 H le 16 avril 2009. Rappelons que “final […]

    Pingback from L’hebdo WordPress : WP 2.8, WP Mu 2.7.1, chasses aux bugs et astuces WP | WordPress Francophone on April 20, 2009

  7. […] possible inclusion in WP 2.8. As you are probably already aware, it wasn’t long ago that the Has-Patch Marathon was announced in a similar “shot gun” fashion. Result of the 24 hour Marathon have […]

    Pingback from Help design dashboard navigation for next WP version | The Shopping Network on April 26, 2009

  8. […] that allow anyone to test the code at any time. It’s worth noting that WordPress recently held a code sprint but given the size of the community, there were relatively few contributions. Many […]

    Pingback from Agile methodologies and open source development | JISCPress on July 6, 2009

See Also:

Want to follow the code? There’s a development P2 blog and you can track active development in the Trac timeline that often has 20–30 updates per day.

Want to find an event near you? Check out the WordCamp schedule and find your local Meetup group!

For more WordPress news, check out the WordPress Planet.


Subscribe to WordPress News

Join 3,075,980 other subscribers

%d bloggers like this: