4.6 Release Dry Run

In preparation for the release on Tuesday, August 16 at 19:00 UTC, we’ll do a dry run on Monday, August 15 at 16:00 UTC.

The dry run will include:

  • Testing various features, including Shiny Updates, native fonts, comment/site/network queries with and without a persistent object cache
  • Generally testing the admin and common features using a multitude of devices and browsers
  • Running our usual unit tests including the specialty groups like multisite, Ajax, and external HTTP
  • Doing scratch installs and upgrades from a variety of older versions
  • Triaging any bugs reported against trunk, most easily found at the top of report 40
  • Updating the credits API
  • Reviewing the Codex release page
  • Moving about page images to the CDN
  • Checking status of translations
  • Reviewing the release post

If you’d like to help out and participate, we’d love to have you. Please come prepared to test!

#4-6, #dry-run

Release Dry Run and Window, RC2 and String Freeze

Hey everyone!

The WordPress 4.5 release proceedings will start at April 12, 2016 at 0900 PDT, with the expectation of release within 2-3 hours of that meeting time. This time allows a decent margin before 5pm EDT (April 12, 2016 at 1400 PDT), at which point a punt to the next day would be discussed.

To help hit that window, let’s meet the day before at April 11, 2016 at 0900 PDT for a dry run.

As a final note, WordPress 4.5 RC2 has been released, and with it, hard string freeze is upon us.

See you at the dry run, and thanks for your help in getting this far!

#4-5, #dry-run

4.2 Release Dry Run

In preparation for a Thursday release, I’d like to do a dry run for 4.2 on Wednesday 15:00 UTC 2015.

The goal would be to complete the dry run and freeze for about a day prior to release. We’ve pushed the scheduled release date by a day due to the 4.1.2 security release that went out on Tuesday morning.

The dry run will include:

  • Testing various features, including Press This and the Customizer Theme Switcher
  • Generally testing the admin and common features using a multitude of devices and browsers, most notably mobile Safari on IOS and IE8
  • Running our usual unit tests including the specialty groups like multisite and AJAX
  • Doing scratch installs and upgrades from a variety of older versions

If we’re satisfied with the results of the dry run, then we’ll freeze. If not, we’ll discuss our options and make a contingency plan going forward.

If you’d like to help out and participate, we’d love to have you. Please come prepared to test!

#4-2, #dry-run

RC2 and release dry run

Various issues which came up over the weekend have meant that we’ve decided to delay the release of 4.1 by another 24 hours. The new target release date is Wednesday 17th December. It doesn’t serve anybody well to delay things this late in the day, but it’s essential to ensure the late fixes which have landed in the last few days are well tested.

RC2 will be packaged within the next few hours, once the recent batch of fixes in trunk are merged into the 4.1 branch. Here’s the current list of open tickets in the 4.1 milestone.

We’ll try to fit in a release dry-run meeting today at 17:00 GMT (December 16 2014 17:00 UTC) in #core, depending on the availability of the lead devs.

#4-1, #dry-run