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.
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...
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.
View Table Headings...
Posted1 day 1 hour ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
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...
In a blog post titled "Github Tips and Tricks for Contrib Maintainers", I'd like to see some of the following topics:
When is the README sufficient for documentation? When should...
Posted2 days 18 hours ago by Olaf Grabienski (Olafski) on:
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?