Nine pull requests are currently marked RTBC - time to consider merging? Bug fixes mostly, and not too complex.
Issue #6987: There's a PoC PR for the "text field Tribbles" problem.
Issue #1528: Another rabbit hole with additional layout paths, it seems. But overall the new approach works pretty well. (Some feedback would be nice.)
Two issues would benefit from testing and code reviews; they've been around for a while and no takers. It would be a shame for these to miss the next releases.
PR improves it significantly but is not a perfect 100% fix at all zoom levels. However, we should not let the desire for perfection prevent incremental improvement.
If anyone has a suggestion to get it to 100%, I'm all ears.
No code reviews or testing yet. I have included a View definition in the issue that requires no additional test data (it is a view of modules) so it can be easily tested in the sandbox.
Short answer: yes.
We are monitoring it for core. And if there are relevant contrib updates we contact the contrib maintainer.
Some of the updates in that feed actually originate...
I'm really hoping to make this simple change on new content types: https://github.com/backdrop/backdrop-issues/issues/7080
Let's disable the "Display author and date information" by...
For our DEV meeting:
an older bug needs (and could have) a fix.
Issue #5729 - Views: Search Filter: On Empty Input "Show None" option Shows All
There are 2 pull requests, but one...
Ruby Text can be a bit of a hassle to edit...
Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Comments
For the dev meeting: Progress all over the place.
Nine pull requests are currently marked RTBC - time to consider merging? Bug fixes mostly, and not too complex.
Issue #6987: There's a PoC PR for the "text field Tribbles" problem.
Issue #1528: Another rabbit hole with additional layout paths, it seems. But overall the new approach works pretty well. (Some feedback would be nice.)
Two issues would benefit from testing and code reviews; they've been around for a while and no takers. It would be a shame for these to miss the next releases.
There are some test failures in the user module after merging in the latest commits.
Randomly, only in one PHP version - and always a different one.
See also this Zulip thread, yorkshirepudding.
Perhaps, these latest lines of random test failures can be considered in the meeting too?