WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#32978 closed task (blessed) (fixed)

Updates to readme.txt files of Bundled Themes

Reported by: mercime Owned by: davidakennedy
Milestone: 4.3 Priority: normal
Severity: normal Version: 4.3
Component: Bundled Theme Keywords: has-patch
Focuses: Cc:

Description (last modified by SergeyBiryukov)

During the course of updating the respective changelog pages of the Bundled Themes in the WP codex, I noticed that the versions of Twenty Fourteen and Twenty Thirteen were not bumped after removing the Genericons example.html files while the Twenty Fifteen version was bumped.

Attached patches bumps versions of Twenty Fourteen and Twenty Thirteen themes in respective style.css and readme.txt files, adds changelogs for the bump in the readme.txt files, and uses SSL for codex URIs for all readme.txt files.

  • twentyfourteen-version-ssl.patch
  • twentythirteen-version-ssl.patch
  • twentyfifteen-ssl.patch
  • twentytwelve-ssl.patch
  • twentyeleven-ssl.patch
  • twentyten-ssl.patch

FYI in preparation for 4.3.0, changelogs of Bundled Themes have been updated in respective pages as of July 12, 2015

To-Dos to complete work started in #31814 and #31074

  • About pages for the Twenty Eleven, Twenty Twelve, and Twenty Thirteen themes. (Finished Twenty Ten. Twenty Fifteen and Twenty Fourteen were prepared before by kpdesign, lancewillet, jdgrimes, siobhan, etc. )
  • Remaining changelogs for earlier versions of Twenty Ten (v 1.1 to 1.6) and Twenty Eleven (v 1.1 to 1.6)

Can work on the above to-dos this coming weekend if no one else does it first and will update http://codex.wordpress.org/WordPress_Default_Themes accordingly.

Attachments (16)

twentyfourteen-version-ssl.patch (3.6 KB) - added by mercime 5 years ago.
twentythirteen-version-ssl.patch (3.5 KB) - added by mercime 5 years ago.
twentyten-ssl.patch (1.6 KB) - added by mercime 5 years ago.
twentyeleven-ssl.patch (2.2 KB) - added by mercime 5 years ago.
twentytwelve-ssl.patch (2.0 KB) - added by mercime 5 years ago.
twentyfifteen-ssl.patch (1002 bytes) - added by mercime 5 years ago.
twentyten.patch (2.7 KB) - added by mercime 5 years ago.
twentyeleven.patch (2.2 KB) - added by mercime 5 years ago.
twentyeleven.2.patch (3.3 KB) - added by mercime 5 years ago.
twentyten-readme.patch (3.3 KB) - added by mercime 5 years ago.
twentyeleven-readme.patch (4.3 KB) - added by mercime 5 years ago.
twentytwelve-readme.patch (3.4 KB) - added by mercime 5 years ago.
twentythirteen-readme.patch (3.4 KB) - added by mercime 5 years ago.
twentyfourteen-readme.patch (2.9 KB) - added by mercime 5 years ago.
twentyfifteen-readme.patch (2.2 KB) - added by mercime 5 years ago.
themeschangelogs.patch (19.5 KB) - added by davidakennedy 5 years ago.
Combine all themes into one patch; update release date.

Download all attachments as: .zip

Change History (38)

#1 @mercime
5 years ago

  • Keywords has-patch added

#2 @samuelsidler
5 years ago

  • Milestone changed from Awaiting Review to 4.3
  • Type changed from enhancement to task (blessed)

@lancewillett: Are you in charge of default theme version bumps this time around? :)

Last edited 5 years ago by samuelsidler (previous) (diff)

#3 @lancewillett
5 years ago

I'd like to nominate @davidakennedy if he's free. I can show him the ropes.

Here's the basic process:

  1. Read each theme's changelog in Trac, and create a changelog file with the highlights (used in Trac tickets, both core and theme review).

http://core.trac.wordpress.org/log/trunk/src/wp-content/themes/twentyfifteen/
http://core.trac.wordpress.org/log/trunk/src/wp-content/themes/twentyfourteen/
http://core.trac.wordpress.org/log/trunk/src/wp-content/themes/twentythirteen/
http://core.trac.wordpress.org/log/trunk/src/wp-content/themes/twentytwelve/
http://core.trac.wordpress.org/log/trunk/src/wp-content/themes/twentyeleven/
http://core.trac.wordpress.org/log/trunk/src/wp-content/themes/twentyten/

  1. Create a new core Trac ticket like #30763 to bump the POT and versions for each theme.
  1. Locally, check out each theme's current WP.org directory version.

http://themes.svn.wordpress.org/twentyten/1.9/
http://themes.svn.wordpress.org/twentyeleven/2.1/
http://themes.svn.wordpress.org/twentytwelve/1.7/
http://themes.svn.wordpress.org/twentythirteen/1.5/
http://themes.svn.wordpress.org/twentyfourteen/1.4/
http://themes.svn.wordpress.org/twentyfifteen/1.2/

  1. Compare with a diff tool to the theme versions in core trunk, is there anything to test or note specifically? Any big unexpected changes?
  1. Test! Load the themes on all recent versions of WordPress: 4.2, 4.1, 4.0, 3.9, etc. Run Theme Check plugin, and check for any errors or things we didn't catch in the core cycle.
  1. Bump the theme versions in core, in each stylesheet.
  1. Wait for the POT update for each theme to be committed, then proceed to make the ZIP packages (might need Nacin or another committer to trigger the POT files update).
  1. Prepare the new version of each theme.
  • svn export from core repository to a temporary location on your local hard drive.
  • Do another quick diff with the previous version for a final sanity check.
  • Zip it: zip -r [name].zip name
  1. After the core release is live, upload the new themes to the WP.org directory as the wordpressdotorg user.

(If needed: note in the ticket, “Do not approve yet, please. We'd like to coordinate with 4.3 release.”)

  1. Ping the release lead as well as Otto to coordinate with the main release process. Otto will approve all the theme changes after the core release is live for everyone.

#4 @obenland
5 years ago

  • Owner set to davidakennedy
  • Status changed from new to assigned

#5 @davidakennedy
5 years ago

Happy to tackle this. Thanks for the nomination! :) I've chatted with Lance a bit, have a good idea of the process, and will set aside time for it.

#6 follow-up: @nacin
5 years ago

Someone please put all of that in the handbook!

#7 in reply to: ↑ 6 @samuelsidler
5 years ago

Replying to nacin:

Someone please put all of that in the handbook!

Your wish is my command.

@davidakennedy: As you run through the process this cycle, please confirm that the handbook page is correct and fix anything that's not or add as much extra information as possible. :)

#8 @obenland
5 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Let's use the Handbook page to continue to track progress.

#9 @samuelsidler
5 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

This ticket isn't about updating the versions of bundled themes, it's about updating and committing the readme files. The patches also include version bumps, but regardless the readme changes are needed.

#10 @obenland
5 years ago

So we keep this open past RC?

#11 follow-up: @obenland
5 years ago

  • Version set to trunk

@samuelsidler, how long do we keep this one open?

This ticket was mentioned in Slack in #core by obenland. View the logs.


5 years ago

#13 in reply to: ↑ 11 @samuelsidler
5 years ago

Replying to obenland:

@samuelsidler, how long do we keep this one open?

Until the patches get committed. That doesn't need to be at RC, just needs to be when we're sure that no further theme changes will be needed. Since this isn't a new theme, that can probably be anytime.

#14 @mercime
5 years ago

The to-do in my post above re changelogs for Twenty Ten (versions 1.1 to 1.6) and Twenty Eleven (versions 1.2 to 1.6) have been completed and posted respectively at

Attached are patches for the readme.txt files of both themes with the links to the updated changelogs and the SSL fixes posted earlier.

As for the About pages in WP Codex for the remaining themes without one, I'm halfway done with Twenty Eleven at http://codex.wordpress.org/Twenty_Eleven
Twenty Twelve and Twenty Thirteen will be done by end of week.

Last edited 5 years ago by mercime (previous) (diff)

@mercime
5 years ago

#15 @ocean90
5 years ago

In 33449:

Bundled Themes: Bump version numbers and update POT files.

see #32978.

#16 @obenland
5 years ago

The only thing missing at this point seems to be the changelogs for all five themes.

#17 @mercime
5 years ago

Attached are updated patches for the readme.txt files of the Bundled Themes.

Last edited 5 years ago by mercime (previous) (diff)

#18 @SergeyBiryukov
5 years ago

  • Description modified (diff)

#19 @davidakennedy
5 years ago

@mercime Thanks for the changelogs – you beat me to it! I updated the Twenty Eleven changlog on the Codex with the skip link change that was committed after your patches.

I'm going to do some additional testing today to make sure I don't see any issues.

I'll wait to make the zip packages until we get closer to release.

@davidakennedy
5 years ago

Combine all themes into one patch; update release date.

This ticket was mentioned in Slack in #core by jorbin. View the logs.


5 years ago

#21 @obenland
5 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

In 33463:

Themes: Update readme files.

Adds information about changes in the current release, links to changlogs from
previous releases, and improves links to use https.

Release date for the latest versions will be August 18 even in the event of a
delayed core release. Since all themes are backwards compatible we don't have
a dependency there.

Props mercime, davidakennedy.
Fixes #32978.

This ticket was mentioned in Slack in #core by davidakennedy. View the logs.


5 years ago

Note: See TracTickets for help on using tickets.