Skip to content

Increase WordPress minimum to 5.2.0#15809

Merged
Soean merged 3 commits intomasterfrom
update/bump-wp-minimum
Nov 12, 2019
Merged

Increase WordPress minimum to 5.2.0#15809
Soean merged 3 commits intomasterfrom
update/bump-wp-minimum

Conversation

@Soean
Copy link
Copy Markdown
Member

@Soean Soean commented May 24, 2019

Description

In WordPress 5.2 the PHP minimum was updated to PHP 5.6.20.

Gutenberg is a feature Plugin for WordPress development. We should set WordPress 5.2 as minimum, so we can remove old PHP compatibility code and tests for old versions.

Related #15796 and #15806

@Soean Soean added the Gutenberg Plugin Issues or PRs related to Gutenberg Plugin management related efforts label May 24, 2019
@youknowriad
Copy link
Copy Markdown
Contributor

We discussed this a little bit here #15565 and there seemed to be an agreement to use 5.1 as a minimum for the moment. What do everyone thinks about moving directly to 5.2. It probably doesn't hurt to wait a few more weeks.

cc @jeremyfelt @aduth @WordPress/gutenberg-core

@nerrad
Copy link
Copy Markdown
Contributor

nerrad commented May 24, 2019

Having usage stats on what wp versions people are using would be helpful here.

With that said, I think its a reasonable assumption that most folks using the plugin understand what it is and are more likely to be on the latest WordPress (or wouldn't have to much issue with getting on the latest WordPress).

@Soean
Copy link
Copy Markdown
Member Author

Soean commented May 24, 2019

Thanks for your feedback.

I understand that we should not increase the minimum too early. But it should also be a goal that users update their WordPress version promptly and don't remain on the same version. If users update their plugins, they are also able to update their WordPress Core.

Yoast recently released a blog post about this topic, in the future they only support the current and the previous major WP version.

This is a feature plugin, so I think we can update the minimum supported version maybe even faster.

Gutenberg 5.9 would be June 12th. (More than a month after WordPress 5.2) or we wait for Gutenberg 6.0 after WordCamp Europe?

@aduth
Copy link
Copy Markdown
Member

aduth commented May 24, 2019

Yoast recently released a blog post about this topic, in the future they only support the current and the previous major WP version.

A takeaway I like from this is to have a policy about it, so it's known and predictable.

It's unclear what benefit there is in waiting? Or in supporting older versions at all? Conversely, there is some benefit in not waiting, as noted by referenced issues of the original comment (removing "baggage").

@youknowriad
Copy link
Copy Markdown
Contributor

Yes, documenting this process would be great. It's not the first time we have a discussion about this. Let's have it once and make it a no brainer for the future.

@designsimply designsimply added the [Type] Task Issues or PRs that have been broken down into an individual action to take label Jun 6, 2019
@gziolo
Copy link
Copy Markdown
Member

gziolo commented Nov 12, 2019

In #18414, I also see a change in the config file for PHPUnit:

<config name="testVersion" value="5.6-"/>

I think Travis file doesn't run PHP 5.2 and 5.3 anymore:
https://github.com/WordPress/gutenberg/blob/master/.travis.yml

@Soean
Copy link
Copy Markdown
Member Author

Soean commented Nov 12, 2019

@gziolo Thanks, I added the change to this PR.

Copy link
Copy Markdown
Contributor

@youknowriad youknowriad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's do that in the next plugin release and maybe even consider 5.3 soon.

@Soean Soean merged commit dc6e470 into master Nov 12, 2019
@Soean Soean deleted the update/bump-wp-minimum branch November 12, 2019 12:57
@youknowriad youknowriad added this to the Gutenberg 7.0 milestone Nov 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Gutenberg Plugin Issues or PRs related to Gutenberg Plugin management related efforts [Type] Task Issues or PRs that have been broken down into an individual action to take

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants