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.7.x plugin upgrade #53135

Closed
36 of 42 tasks
fullofcaffeine opened this issue May 25, 2021 · 1 comment
Closed
36 of 42 tasks

Gutenberg: v10.7.x plugin upgrade #53135

fullofcaffeine opened this issue May 25, 2021 · 1 comment
Assignees
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 May 25, 2021

Previous upgrade: #52595
Release notes: v10.7.0-rc.1, v10.7.0, v10.7.1.

  • Install and activate
    • Copy & install v10.7.0-rc.1 (D61793-code, D61795-code)
    • Hotfix v10.7.0-rc.1 on edge to fix the WSOD issue (more details below) (D61799-code, D61800-code)
    • Activate v10.7.0-rc.1 on edge (D61797-code) (Blocked, needs [ETK/wpcom-block-editor] Use __unstable InserterMenuExtension if available, fallback to __experimental #53131 to be shipped)
    • Copy & install v10.7.0 (D61918-code, D61920-code)
    • Hotfix v10.7.0 on edge to fix the WSOD issue (more details below) (D61922-code, D61923-code)
    • Activate v10.7.0 on edge (D61929-code)
    • Copy & install v10.7.1 (D61941-code, D61943-code)
    • Hotfix v10.7.1 edge to fix the WSOD issue (more details below) (D61944-code, D61945-code
    • Activate v10.7.1 on edge (D61948-code)
    • Make sure there are no active blockers
    • Activate v10.7.1 on production (D61050-code)
    • Merge E2E test fixes: E2E fixes for Gutenberg 10.6.x / 10.7.x #52832 (this will effectively revert this commit. Context)
    • Request AT upgrade
    • Copy & install v10.7.4 (D62431-code, D62432-code)
    • Hotfix v10.7.4 to fix the WSOD issue (D62433-code)
    • Activate v10.7.4 on edge (D62435-code)
    • Request AT upgrade
  • Testing
    • Desktop viewport E2E
    • Mobile viewport E2E (p1622745527036300-slack-C1A1EKDGQ)
    • WPCOM Backend (D61050-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 🙅‍♀️

This has been fixed in the PR and merged, but is yet to be deployed to WPCOA/WoA. Even though we could get it on simple sites now, it's best to wait until the next Jetpack release on June 1st for the new JP release or people that upgrade to WoA will get invalidation errors with the Premium Content block. More details in this thread: p1621442044054200-slack-CBG1CP4EN.

Other issues 🐛

From the new release

Transfered from previous release(s)

  • wp-components's index.js is broken by the WPCOM minifier. There's a hotfix (D61090-code, D61091-code) applied in the RC1 that allowed us to ship it to simple sites for now. We still don't know what exactly in v10.6.0 RC1 caused this. We might need to be hotfixing on simple sites while we don't have a perm. solution. See: p1620321684463200-slack-C02A41GCS and p1620319065221200-slack-C4GAP2RHD.

  • 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).

  • Classic: Infinite content duplication loop when wrapping with anchor tag #29338

    • Reported in: p1613735197155300/1613458151.107400-slack-CBTN58FTJ
  • Search block's button padding is broken


cc @inaikem

@fullofcaffeine
Copy link
Contributor Author

Next one: #53394.

@fullofcaffeine fullofcaffeine self-assigned this Jun 15, 2021
@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

1 participant