- Issue created by @trackleft2
- πͺπΈSpain isholgueras
I was creating the issue for 4.0.21 until I realized you also created it.
I was wondering to if it makes sense to plan this release (maybe one more release) to be the latest release before 4.1. I wouldn't like to maintain 2 different version unless it's strictly necessary.
I would like to add to this release these issues (some leftovers from 4.0.20 release and some new)
Release-blocker issues (Bug fixes)
- π Gin vertical toolbar submenu's overlap Active
Good-to-fix issues (Good to have)
- π Fix cspell issues Active
- π Coding standards and best practices Active
- π Documentation guide update Needs review
- π± Move toolbar integration into submodule. Active
- π Hostname field isn't a hostname but a base URL Active
- #3065135: Add support for multilingual domain sites β
There are more issues I would like to work on and add to the release, but at least this is a good amount of issues to include in 4.0.21. What do you think?
- πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
Thanks for merging. I think your list looks good, and possibly π Environmental indicator incorrect version identifier Active
IMHO we should start dropping support for older versions of Drupal core with the first minor release (4.1.0), so we can begin to take advantage of some of the newer OOP patterns and core features.
- πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
Let's work on merging the code quality merge requests and fixing the inevitable merge conflicts that will occur as a result. I'll volunteer to update any merge requests that need it.