-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrading to WordPress 5.0 #96
Comments
I've done mine. @wunluv @DavidScottBernstein Please post here when you've done yours. |
Done. Updated Wordpress to 5.0 and updated the Wordpress database. |
There is now a quick bug-fix update to WP 5.01. I recommend that people just do these minor upgrades as a matter of course. |
Should we lean towards doing these kind of major updates in a branch other than master. I suggest that unless its an important security patch issued by an upstream dependency, additions to our master dev branch shouldn't contain any major dependency upgrades until its been tested in breakable dev branch. |
That sounds like a good caution once we are further along but for now, in our current alpha state, I lean more to skating where the puck will be. I did test the update locally before recommending it to the group and probably should have said that in my initial post. |
Also note that our repository is just one subfolder in the WordPress install. Things like these updates probably don't even touch the repository. |
Briefly, I recommend that we all do the upgrade.
The major change in 5.0 is the shift to the Gutenberg editor – a shift that won't have much impact on our BuddyPress-based site. For others, however, it's a big shift with a lot of controversy around it.
In any case, go to Admin Dashboard > Updates and do the usual.
The text was updated successfully, but these errors were encountered: