Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#46070 closed task (blessed) (fixed)

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

Reported by: laurelfulford's profile laurelfulford Owned by: laurelfulford's profile laurelfulford
Milestone: 5.1 Priority: normal
Severity: normal Version:
Component: Bundled Theme Keywords: has-patch commit
Focuses: Cc:


Since 5.1 will ship with some fixes to default themes, let's add a Task to bump each theme’s version number and update each changelog.

Handbook page:

Previous related tickets for reference: 5.0.3: #45792 5.0.2: #45681.

Attachments (2)

46070.patch (31.9 KB) - added by laurelfulford 5 years ago.
46070.2.patch (33.6 KB) - added by laurelfulford 5 years ago.

Download all attachments as: .zip

Change History (12)

5 years ago

#1 @laurelfulford
5 years ago

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

#3 @laurelfulford
5 years ago

Gah, thank you for catching that, @allancole! :| You'd think I'd never done this before.

Creating a new patch now!

#4 @laurelfulford
5 years ago

46070.2.patch should be correct -- @allancole can you please take a second look when you have a chance? Thanks!

#5 @allancole
5 years ago

I think this looks good @laurelfulford


#6 @ianbelanger
5 years ago

  • Keywords needs-testing removed

I second @allancole in saying that everything looks good on this patch. I say ship it.

#7 @laurelfulford
5 years ago

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

#8 @pento
5 years ago

  • Keywords commit added

Looks good, let's go!

#9 @laurelfulford
5 years ago

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

In 44730:

Default Themes: Bump the version numbers and release dates.

Update the theme versions and release dates for the default themes, in time for WordPress 5.1.

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

Fixes #46070.

#10 @laurelfulford
5 years ago

Thanks @allancole, @ianbelanger & @pento!

Note: See TracTickets for help on using tickets.