WordPress.org

Making WordPress.org

Opened 2 months ago

Closed 8 weeks ago

#5012 closed task (fixed)

Remove Twenty Sixteen from WordPress >= 5.2 builds

Reported by: desrosj Owned by:
Milestone: Priority: normal
Component: General Keywords:
Cc:

Description

I did some research following the inquiry from @joyously in a recent Slack discussion about how many default themes are usually bundled in new installs.

It seems that since version 3.7, only the three most recent default themes were included in new installs. That remained true until 5.2 when Twenty Twenty was introduced and Twenty Sixteen was not trimmed from the list (this was an oversight).

Not sure if there is a better place to make this sort of request. I couldn't find tickets for similar requests in the past here on Meta Trac. Please feel free to direct me to the better location.

Change History (9)

#1 @desrosj
2 months ago

I realize it may not be possible or necessary to remove Twenty Sixteen from 5.2 and 5.3 because those have already been released, but wanted to report those versions as where the problem began and exists.

This ticket was mentioned in Slack in #core-themes by desrosj. View the logs.


2 months ago

#4 @dd32
2 months ago

Seems reasonable to me.

FWIW, here's the list of default themes, and the versions they were NOT shipped with:

Theme, Removed in package versions
twentyten >= 3.6
twentyeleven >= 3.7
twentytwelve >= 4.2
twentythirteen >= 4.5
twentyfourteen >= 4.7
twentyfifteen >= 5.0

#5 follow-up: @Otto42
2 months ago

Seems like this should be a core ticket, since that's the core build process.

#6 in reply to: ↑ 5 ; follow-up: @dd32
2 months ago

Replying to Otto42:

Seems like this should be a core ticket, since that's the core build process.

It's a murky area, since the build processes and things like SVN happen in meta (Well Mission Control in this case).

I'd prefer to see some discussion and consensus from Core before this change is made though.

Also worth mentioning, that any change here will probably be 5.4+ since there's probably not going to be any significant number of 5.3.x releases before 5.4.

#7 in reply to: ↑ 6 @desrosj
2 months ago

Replying to dd32:

I'd prefer to see some discussion and consensus from Core before this change is made though.

Fair enough. I did some searching but I could not find this documented anywhere. I feel like it may be buried in the Core or default theme handbooks somewhere.

#8 follow-up: @ocean90
8 weeks ago

In the past I have done the patch and sent it to @dd32 for commit ([dotorg14572]). Looks like I missed that this time. The build process for localized packages was updated in [dotorg15446], though, so those only contain the the last three themes.
It don't see why we can't make this change now even if it only applies to upcoming (minor) versions.

#9 in reply to: ↑ 8 @dd32
8 weeks ago

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

Replying to ocean90:

In the past I have done the patch and sent it to dd32 for commit ([dotorg14572]). Looks like I missed that this time. The build process for localized packages was updated in [dotorg15446], though, so those only contain the the last three themes.
It don't see why we can't make this change now even if it only applies to upcoming (minor) versions.

Works for me.. Fixed in [dotorg15749].

TwentySixteen will no longer be included in 5.3.x+ builds. Existing builds will remain unchanged.

Note: See TracTickets for help on using tickets.