Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#35270 closed task (blessed) (fixed)

Bump twentysixteen for 4.4.1

Reported by: jorbin's profile jorbin Owned by: otto42's profile Otto42
Milestone: 4.4.1 Priority: normal
Severity: normal Version:
Component: Bundled Theme Keywords:
Focuses: Cc:

Description

twentysixteen will have a new version that should be included in 4.4.1 @dd32 and @karmatosed are coordinating.

Change History (11)

#1 @jorbin
10 years ago

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

#2 @SergeyBiryukov
10 years ago

  • Component changed from Themes to Bundled Theme

#3 @dd32
10 years ago

I've bumped the cache busters in twentysixteen in https://github.com/WordPress/twentysixteen/pull/405

This can ride until just before 4.4.1's release on Jan 8th, as the 4.4.1-RC builds will include master from Github. The 4.4.1 build will include the latest release from the themes directory (Please allow for the up-to-15 minute cache, and double check the copy inside the zip after build).

I can either use my script (the one I used for nightly builds) to pull the TwentySixteen build into the Themes Directory (As I did for the initial release), or @otto42 or someone can import it manually as we've done with all previous default themes.

When pulling it in from Github the following files should be skipped:

  • All files beginning with .
  • All files ending in .md
  • codesniffer.ruleset.xml.
Last edited 10 years ago by dd32 (previous) (diff)

#4 @Otto42
10 years ago

  • Owner changed from karmatosed to Otto42

No need to make it complicated. I can upload the zip and approve it for the directory in a few minutes. Just need to be pinged as to when it becomes necessary. Loop me in and I'll handle it.

#5 @Otto42
10 years ago

Question: is the new twenty sixteen dependent on 4.4.1? If not, we can release it at any time prior. The core bundling is totally separate and irrelevant to updates anyway.

#6 @karmatosed
10 years ago

@Otto42 no it's not, but we bumped the version now anyway. It would be great to release the same time of 4.4.1 as there is a new version of 1.1.

We have frozen Twenty Sixteen ready to release. The version is bumped and new contributors added.

It's worth noting for whoever does the upload that in the file: https://github.com/WordPress/twentysixteen/blob/master/CONTRIBUTORS.md there is a 1.1 section with the new contributors there.

Last edited 10 years ago by karmatosed (previous) (diff)

#7 @dd32
10 years ago

I thought I'd left a comment here already to this effect, but please do not release twentysixteen prior to the 4.1.1 release timeslot.

There's no urgency in the release of it, and we don't need yet-another update nag as soon as someone installs WordPress.

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


10 years ago

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


10 years ago

#10 @Otto42
10 years ago

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

Twenty Sixteen uploaded to themes directory:

https://themes.trac.wordpress.org/ticket/29656

Coordinating with #core on release timing now.

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


10 years ago

Note: See TracTickets for help on using tickets.