Release Day Checklist

Release Candidate (RC1)

  • Post the BBQ DRAFT as soon as RC1 is released.

Top ↑

Release day

  1. Make sure all posts in Alpha/BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. are resolved, closed, or moved out.
  2. Update BBQ DRAFT post with the real urls of the release and it’s name.
  3. AFTER The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. posts the release, you can make the BBQ forum post.
  4. Update IRC topics with the new stable version number and announcement post when this goes live.
  5. Update the links for the latest major WordPress release (and new default theme if applicable) on
  6. Keep chatter and emoji in #forums to a minimum for 48 hours after release in order to not lose legit questions or issues.

Top ↑

Days following a release

  • Make a list of all issues to present in next #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. meeting.

Top ↑

The BBQ Post

  • Title the post READ THIS FIRST WordPress {{VERSION}} Master List
  • Each section should be their own reply (for easier editing).

Last updated: