[wp-trac] [WordPress Trac] #36497: Merge Twentysixteen with the rest of WordPress Core

[WordPress Trac]

#36497: Merge Twentysixteen with the rest of WordPress Core
----------------------------+------------------------------
 Reporter:  jorbin          |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Bundled Theme   |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by davidakennedy):

 I've helped test and package the changes in all default for release in the
 theme directory for the past few releases. I watch and test all the
 changes in default themes as a result. Having Twenty Sixteen in a
 different place with a different flow certainly makes those tasks more
 time consuming and a bit harder. That said, the slow down during the 4.5
 release was really due to the different process for Twenty Sixteen not
 being written down somewhere, and all those involved not knowing enough
 about it. Myself included. The process is slightly different for a release
 than a beta or release candidate, which is confusing.

 All that said, I'd be willing to let Twenty Sixteen and future default
 themes remain on Github if it meant that the themes saw more bug fixes and
 features implemented by more contributors. That happened when Twenty
 Sixteen was first in active development on Github. That's great for
 WordPress and themes. And we can figure out the tooling and processes to
 make this better. I don't think that's an obstacle.

 If you look at the changelogs for the themes this release (4.5), there
 isn't a noticeable difference between the amount of work on Twenty Sixteen
 vs. default themes in Core. See: #36354 and
 http://codex.wordpress.org/Twenty_Sixteen_Theme_Changelog#Version_1.2

 So I'd be in favor of meeting in the middle. A new default theme gets
 developed on Github (as long as that makes sense), and then when WordPress
 reaches release candidate for that release or the theme is considered
 stable, the theme is merged and maintenance happens in Core.

 We can always change paths later too, if we decide a new way is better.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36497#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform