Skip to content
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

Gutenberg: v10.8.x plugin upgrade #53394

Closed
36 of 38 tasks
fullofcaffeine opened this issue Jun 3, 2021 · 3 comments
Closed
36 of 38 tasks

Gutenberg: v10.8.x plugin upgrade #53394

fullofcaffeine opened this issue Jun 3, 2021 · 3 comments
Labels
gutenberg-upgrade To be used to classify Gutenberg upgrade tracking issues and make it easier to list them [Type] Task

Comments

@fullofcaffeine
Copy link
Contributor

fullofcaffeine commented Jun 3, 2021

Previous upgrade: #53135.
Release notes: v10.8.0-rc.1, v10.8.0, v10.8.1.

  • Install and activate
    • Copy & install v10.8.0-rc.1 (D62496-code, D62496-code)
    • Hotfix v10.8.0-rc.1 on edge to fix the WSOD issue (D62506-code)
    • Activate v10.8.0-rc.1 on edge (D62505-code)
    • Copy & install v10.8.0 (D62579-code, D62580-code)
    • Hotfix v10.8.0 on edge to fix the WSOD issue (D62581-code)
    • Activate v10.8.0 on edge (D62583-code)
    • iframe-server callback store fix (D62881-code)
    • Copy & install v10.8.1 (D62884-code, D62885-code)
    • Hotfix v10.8.1 on edge to fix the WSOD issue (D62887-code) >> last time we have to do this! << 🎉
    • Activate v10.8.1 on edge (D62888-code)
    • Activate v10.8.1 on production (D62508-code)
    • Request AT upgrade
    • Copy & install v10.8.2 (D62936-code, D62937-code)
    • Prepare a custom v10.8.2-with-min-js-assets based off this branch (D62953-code)
    • Copy v10.8.2 to custom v10.8.2-with-min-js-assets (D62949-code, D62954-code)
    • Activate v10.8.2-with-min-js-assets on edge (D62956-code)
    • Run tests for v10.8.2-with-min-js-assets - E2E and WPCOM
    • Fix WPCOM tests for v10.8.2-with-min-js-assets (D62958-code)
    • Deploy v10.8.2-with-min-js-assets to prod (D62958-code)
    • Request AT upgrade for v10.8.2
  • Testing
    • Desktop viewport E2E
    • Mobile viewport E2E
    • WPCOM (D62508-code)
  • Publish internal announcements
  • Clean up unused releases
  • Add log entry to the Gutenberg Upgrade Log [pcoGjb-g-p2]
  • Open a new issue for the next upgrade, transfer remaining tasks, close this issue.

Blockers 🙅‍♀️

Other issues 🐛

Transfered from previous release(s)


cc @inaikem

@fullofcaffeine
Copy link
Contributor Author

P2 inline comments broken (and potentially other P2-related issues). Reported here: p1620327615008700-slack-C025Q5RK2 cc @johngodley (P2s have been pinned to 10.5.4 for now, see: p1621258202222400/1620838719.129600-slack-C7YPUHBB2, which makes this issue not a blocker for now).

@johngodley Is this still an issue?

@fullofcaffeine
Copy link
Contributor Author

Next one: #53725.

@johngodley
Copy link
Member

@johngodley Is this still an issue?

Kind of, but for a different bug introduced in Gutenberg 10.7.x and fixed in 10.8. P2 itself has been updated and should run fine on 10.7 and 10.8. I'll wait for 10.8 to settle down and if it's solid I'll unpin P2, otherwise I have a fix for 10.7 to get it running there.

@fullofcaffeine fullofcaffeine added the gutenberg-upgrade To be used to classify Gutenberg upgrade tracking issues and make it easier to list them label Jul 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gutenberg-upgrade To be used to classify Gutenberg upgrade tracking issues and make it easier to list them [Type] Task
Projects
None yet
Development

No branches or pull requests

2 participants