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.
Posted2 weeks 6 days ago by Erik Wesselius (zilvervos) in Other
Recent comments
The issue with checking for updates in the BackdropCMS dashboard makes website development and maintenance more difficult. I manage more than ten websites hosted by two different providers, one...
Recently came back to see if translation issues are fixed, with the latest version:
Page translations are fixed, but the issue with taxonomy and menus are still there. Localized terms show...
Possible agenda item: For docs.borg, maybe the non-code syntax related documentation and policies should go under a new "Organization Policies" section? Not the most pressing or exciting idea...
For reference on #2, I did open an all-encompassing issue for the technical side (I haven't had time to work on it yet): https://github.com/backdrop-ops/backdropcms.org/issues/1107
As for...
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?