WordPress.org

Make WordPress Core

Opened 6 months ago

Closed 4 months ago

#45167 closed task (blessed) (fixed)

Bundled Themes: Bump version numbers and update changelogs for 5.0 release

Reported by: laurelfulford Owned by: laurelfulford
Milestone: 5.0 Priority: normal
Severity: normal Version: 5.0
Component: Bundled Theme Keywords: has-patch fixed-5.0
Focuses: Cc:

Description (last modified by laurelfulford)

Since 5.0 will ship a patches to add Gutenberg styles and support for Twenty Ten through Twenty Seventeen, let's add a Task to bump each theme’s version number and update each changelog.

Related tickets:

Handbook page: https://make.wordpress.org/core/handbook/about/release-cycle/update-bundled-themes/

Previous related tickets for reference: 4.9.5 #43572 4.9: #42090

Attachments (7)

45167.patch (13.3 KB) - added by laurelfulford 6 months ago.
45167.1.patch (40.6 KB) - added by laurelfulford 6 months ago.
45167.2.patch (40.5 KB) - added by laurelfulford 6 months ago.
45167.3.patch (80.6 KB) - added by maedahbatool 5 months ago.
👌 IMPROVE: Update latest theme stable versions
45167.4.patch (96.0 KB) - added by mrahmadawais 5 months ago.
👌 IMPROVE: Theme stable versions for twenty thirteen & twelve
45167.5.patch (44.0 KB) - added by laurelfulford 5 months ago.
45167.6.patch (44.0 KB) - added by laurelfulford 5 months ago.

Download all attachments as: .zip

Change History (27)

#1 @laurelfulford
6 months ago

  • Description modified (diff)

#2 @laurelfulford
6 months ago

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

#3 @SergeyBiryukov
6 months ago

  • Milestone changed from Awaiting Review to 5.0

#4 @laurelfulford
6 months ago

  • Keywords has-patch needs-testing added; needs-patch removed

#5 @laurelfulford
6 months ago

45167.patch bumps all the version numbers, and adds links to where the new changelogs will be.

#6 @davidakennedy
6 months ago

  • Keywords commit added; needs-testing removed

Hi @laurelfulford! I reviewed this patch, and it looks ready. Marking it as such.

#7 @laurelfulford
6 months ago

I belatedly realized that I also should have included the new POT files for Twenty Ten and Eleven in this commit -- I've done that in 45167.1.patch.

@davidakennedy whenever you can give this one more once over, I'd appreciate it!

#8 @laurelfulford
6 months ago

Updated 45167.2.patch to include the change in line numbers that would have happened in Twenty Eleven's functions.php from #45274.

#9 @davidakennedy
6 months ago

Looks good, @laurelfulford. Thanks for the update.

#10 @pento
5 months ago

Patch looks good, lets hold off on committing it until we're in RC and there are no more changes to land.

@maedahbatool
5 months ago

👌 IMPROVE: Update latest theme stable versions

@mrahmadawais
5 months ago

👌 IMPROVE: Theme stable versions for twenty thirteen & twelve

#11 @maedahbatool
5 months ago

🙌 Hey, @laurelfulford!

I just added the stable versions of the latest WordPress themes. Kindly, take a look at it.

Cheers! ✌️

#12 @mrahmadawais
5 months ago

👋 @maedahbatool looks like you missed TwentyThirteen and TwentyTwelve so I patched that as well.

👋 @laurelfulford take a look at the final patch from @maedahbatool and me. :)

Looking forward to WP 5.0!

Peace! ✌️

#13 follow-ups: @laurelfulford
5 months ago

Thanks so much @maedahbatool and @mrahmadawais for catching that, and your patches!

45167.5.patch contains the exact same changes as 45167.4.patch. The updates in 45167.4.patch look good, but for some reason the patch itself makes it look like entire readme files in a couple of the themes have changed. That doesn't actually happen when you apply the patch; I made the new one just to prevent confusion once we're ready to commit. :)

#14 in reply to: ↑ 13 @maedahbatool
5 months ago

Replying to laurelfulford:

Thanks so much @maedahbatool and @mrahmadawais for catching that, and your patches!

Thanks a ton. 💯

45167.5.patch contains the exact same changes as 45167.4.patch. The updates in 45167.4.patch look good, but for some reason the patch itself makes it look like entire readme files in a couple of the themes have changed. That doesn't actually happen when you apply the patch; I made the new one just to prevent confusion once we're ready to commit. :)

Awesome! Makes sense. Looking forward to the final commit. ✌️

#15 in reply to: ↑ 13 @mrahmadawais
5 months ago

Replying to laurelfulford:

Thanks so much @maedahbatool and @mrahmadawais for catching that, and your patches!

Happy to help and contribute. 🐨

45167.5.patch contains the exact same changes as 45167.4.patch. The updates in 45167.4.patch look good, but for some reason the patch itself makes it look like entire readme files in a couple of the themes have changed. That doesn't actually happen when you apply the patch; I made the new one just to prevent confusion once we're ready to commit. :)

Strange. I saw that too, but there were no changes. Must be prettier rewriting the entire file for formatting sake or SVN.

Peace! ✌️

#16 @laurelfulford
5 months ago

45167.6.patch updates the release dates in all of the theme's readme files, to match the new date shared here: https://make.wordpress.org/core/2018/11/09/update-on-5-0-release-schedule/

#17 @pento
5 months ago

  • Keywords needs-refresh added; commit removed

45167.6.patch will need a refresh when there's a new release date announced.

#18 @pento
5 months ago

In 43964:

Default Themes: Bump the version numbers and release dates.

With WordPress 5.0 just a few short days away, the default themes can have their version numbers bumped.

The POT files for Twentys Ten and Eleven have also been updated.

Props laurelfulford, maedahbatool, mrahmadawais, pento.
See #45167.

#19 @pento
5 months ago

  • Keywords fixed-5.0 added; needs-refresh removed

#20 @desrosj
4 months ago

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

In 44279:

Default Themes: Bump the version numbers and release dates.

The POT files for Twenty Ten and Eleven have also been updated.

Props laurelfulford, maedahbatool, mrahmadawais, pento.

Merges [43964] into trunk.

Fixes #45167.

Note: See TracTickets for help on using tickets.