- Issue created by @dww
- 🇺🇸United States dww
Note: I see the D12 compatibility was added so that the upgrade_status job would "work" when run against 11.1.x core. This is the wrong approach. It's pointless to run the upgrade_status job on every MR pipeline until you're actually getting ready to port to D12.
- 🇮🇳India akulsaxena
Good point, I think removing the upgrade status and core version requirement for D12 is fine until D12 is released and ready.
The changes look good to me. Will wait for one of the maintainers to have a look too before it is moved to RTBC+ -
vladimiraus →
committed 39ecf5f7 on 3.0.x authored by
dww →
Issue #3503220: Premature declaration of D12 compatibility
-
vladimiraus →
committed 39ecf5f7 on 3.0.x authored by
dww →
- 🇦🇺Australia VladimirAus Brisbane, Australia
Thanks everyone. Adding to release. 🍻
Automatically closed - issue fixed for 2 weeks with no activity.