In #3079680: [META] Requirements for tagging Drupal 9.0.0-beta1, we define must-haves and should-haves for tagging beta1. Some should-haves may cause Drupal 9.0.0-beta1 to be deferred to one of the predefined fallback windows, but we may allow some to be completed during the beta and release candidate phases.
This is a stub issue for tracking critical beta target tasks that should happen during the Drupal 9.0 beta phase following 9.0.0-beta1. At a minimum, it will include any should-haves from #3079680: [META] Requirements for tagging Drupal 9.0.0-beta1 not completed by 9.0.0-beta1.
It may include other tasks for core, Drupal.org, documentation, ecosystem tools, etc.
Critical regressions due to recent commits, bugs affecting the upgrade and migration paths to 8.9 and 9.0
(*) We won't actually delay the scheduled release once we've locked in a beta scenario, but we might delay 9.0.0-rc1 for them.
Comments
Comment #2
xjmComment #3
gábor hojtsy#3090183: UPGRADE.txt only mentions migrating from Drupal 6 and 7, UPDATE.txt only mentions 8-8 updates looks like one :)
Comment #4
xjmComment #5
xjmComment #6
xjmComment #7
xjmComment #8
xjmComment #9
catchComment #10
catchComment #11
catchComment #12
catchComment #13
catchComment #14
catchComment #15
catchComment #16
catchComment #17
ankush_03Comment #18
xjmComment #19
gábor hojtsyUpdated the three must-haves that are done with DONE.
Comment #20
gábor hojtsyFix beta targets link.
Comment #21
shaktikComment #22
xjmDeclaring a few more issues as must-haves.
Comment #23
xjmComment #24
xjmComment #25
dwwI spun off #3131950: UX review of the finished, semver-compliant update status report for how it presents the Drupal 8.9 and 9.0 updates for users on various versions as an actual issue. Still "Needs triage". I tagged it "9.0.0-rc1 requirement", which may or may not be accurate. ;)
Comment #26
xjmAdded #3123537: /admin/reports/status should not WSOD if it finds an extension missing core_version_requirement in its info.yml file as a must-have for now. (It's at least a should-have.)
Comment #27
gábor hojtsyUpdating two more are done.
Comment #28
xjm#3120910: Sites with missing schema information can't update to 8.8.3+ - attempts to run all historical updates is in as well.
Comment #29
xjmComment #30
xjmComment #31
xjmComment #32
gábor hojtsyComposer 2 compatibility also landed.
Comment #33
xjmA couple "DONE" things got un-done last night because of a serious issue we were having with composer updates installing dev minor releases
Comment #34
xjmComment #35
xjmComment #36
xjmJust to clarify that 8.9.x issues are a part of this too, since 8.9 and 9.0 have the same (non-deprecated) API.
Comment #37
webchickSorry, my inner pedant just couldn't let that one go. ;)
Comment #38
xjmComment #39
xjmI am trying to figure out why the IS isn't actually udpating.
Comment #40
xjmOK, was a markup failure.
Comment #41
xjmComment #42
dwwAdding #2625136: Fix label visibility and add wrapper container for exposed numeric/date filters with multiple form elements as needs triage. It's a major accessibility bug. The fix is somewhat disruptive (changes the form structure of views exposed forms in some cases). It seems much better to fix before RC than to try to fix between RC and final, and definitely better to not do as a patch release fix (e.g. in 8.9.1 or 9.0.1), as confirmed by @catch during the last #d9readiness meeting. I don't feel authorized to add it directly to "Should have", but I wanted to get some more eyeballs on it ASAP. ;)
Thanks!
-Derek
Comment #43
xjmComment #44
xjmAdding #3135629: Minimum MySQL version requirement is not confirmed when upgrading existing sites from Drupal 8 to Drupal 9 which gets harder to fix as we get closer to a production release.
Comment #45
xjm@dww, #2625136: Fix label visibility and add wrapper container for exposed numeric/date filters with multiple form elements is a major bug, but not really different from any other major bug and it doesn't have any specific relationship to the D9 requirements. You're right that it might be a minor-only bugfix, but it's not major-only, nor related to the upgrade path, so it's not needed to track it here.
Comment #46
xjmAdding #3135034: 8.9.x-dev tarball INCLUDES CODER AS A MODULE (!) because Composer packages.drupal.org definition incorrect for Coder 8.3.9 because creating an 8.9.0 release that might overwrite something in someone's modules directory ain't cool.
Comment #47
drumm8.9.0 should not be affected by #3135034: 8.9.x-dev tarball INCLUDES CODER AS A MODULE (!) because Composer packages.drupal.org definition incorrect for Coder 8.3.9 since tagged release tarballs do not include dev dependencies. Coder is a dev dependency.
Comment #48
dww@xjm Re: #45: The reason I mentioned #2625136: Fix label visibility and add wrapper container for exposed numeric/date filters with multiple form elements here is that it seems that the window to fix this bug anytime this year is rapidly closing, and I was hoping we could solve it now instead of punting to 9.1.0 (at the earliest). The reason it's not necessarily like most other RTBC major bugs is that it's probably not fixable between rc and final, nor in a patch release. I assume you're not going to want to fix it after rc1, so I was trying to get it in before that happens, and therefore posted here. Trying to remove technical debt (known bugs) from the next round of stable releases. 🤞 /shrug
Comment #49
xjmComment #50
xjmComment #51
xjm@dww Yeah, it's not a should-have, just a minor-only major bug, so removing it from the list. Thanks!
Comment #52
xjmAdding #3136668: Invalid system.schema key_value entry causes fatal on updating to 8.8.5 which is apparently a regression after 8.8.3?
Comment #53
catchThat will affect sites updating to 8.7.13 too, although only if they already have corrupted system.schema information in that specific way.
Comment #54
xjmComment #55
catchComment #56
gábor hojtsyThe release candidate is now out, so closing.