Bundled Themes: Bump version number and update changelog in Twenty Seventeen for 4.9.8 release

[pbiron]

Since 4.9.8 will probably ship a patch to address level 2 bulleted lists nesting in Twenty Seventeen, let's add a Task to bump the version number and update the changelog.

Twenty Seventeen is the only concerned theme. Related ticket: #44109

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 4.8: #40905

Note: If #44109 is finally not shipped with 4.9.8, then this task may be closed.

[pbiron]

Bump version number and update changelog in Twenty Seventeen for 4.9.8 release

[laurelfulford]

Thanks for taking care of this, @pbiron!

I can review and commit later today or tomorrow!

[laurelfulford]

In 43541:

Twenty Seventeen: Bump version number and update changelog for 4.9.8 release.

Props pbiron.
Fixes #44646.

[laurelfulford]

Following up to say I've updated the changelog as well: ​https://codex.wordpress.org/Twenty_Seventeen_Theme_Changelog#Version_1.7

[celloexpressions]

Is it worth forcing every WordPress site that hasn't deleted this default theme to run an update that fixes one issue? While it's great to ship fixes to issues frequently, the update process is manual for nearly all users, and this theme is installed (but unused) on nearly all WordPress sites. The recent frequency of minor default theme releases is starting to be problematic for update fatigue.

Can we triage and incorporate some additional fixes before bundling a release, perhaps alongside 4.9.9? There are many other reported issues against Twenty Seventeen that would be worth fixing: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=Bundled+Theme&summary=~Twenty+Seventeen&order=milestone

Historically, releasing bundled theme updates alongside core major releases 2-3 times a year has resulted in a reasonable balance between speed of development and frequency of updates. We're drifting pretty far in one direction with the current plan to ship a one-change update alongside 4.9.8, following two other smaller theme updates in the past few months. Reopening for visibility and discussion.

[laurelfulford]

Thanks for the feedback, @celloexpressions! I think it’s best to keep this update in 4.8.9, especially given where we are in the release cycle. But I think this is a really good point, and something to keep in mind with future releases.

[laurelfulford]

44646.2.diff​ updates the release date to August 2, 2018.

[davidakennedy]

@laurelfulford 44646.2.diff looks good to go.

[laurelfulford]

In 43550:

Twenty Seventeen: Correct date in changelog for 4.9.8 release.

Props pbiron, laurelfulford.
Fixes #44646.

[laurelfulford]

I updated the date here as well:

​https://codex.wordpress.org/Twenty_Seventeen_Theme_Changelog#Version_1.7

[SergeyBiryukov]

In 43551:

Twenty Seventeen: Bump version number and update changelog for 4.9.8 release.

Props pbiron, laurelfulford.
Merges [43541] and [43550] to the 4.9 branch.
Fixes #44646.