@rogelio - Thanks for reporting this. When you are in doubt, this is always a good place to ask your question or raise your concern.
I don't have a technical response for you, but I can make a process suggestion.
1) If you have the time and/or skills to provide more information about what is or is not happening, that would be really helpful and might help triage which module is causing the problem. Provides step by step guide to reproduce the problem is HUGELY helpful.
2) If not sure which module is causing the problem, I think it's appropriate to take your best guess and pick one or simply go ahead and open an issue in both issue queues. Be clear in your description of the issue that it involves two modules and you are not clear which is causing the problem (maybe both). If opening issues in both queues, I would add a link to the respective issue in the other queue.
If either module maintainer can verify the the problem is not with their module, they can easily close the issue and no harm is done.
As usual, you are much more likely to get results/help if you are able to provide the clearest and easiest possible step by step guide to reproduce the problem.
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 17 hours ago by Olaf Grabienski (Olafski) on:
Comments
@rogelio - Thanks for reporting this. When you are in doubt, this is always a good place to ask your question or raise your concern.
I don't have a technical response for you, but I can make a process suggestion.
1) If you have the time and/or skills to provide more information about what is or is not happening, that would be really helpful and might help triage which module is causing the problem. Provides step by step guide to reproduce the problem is HUGELY helpful.
2) If not sure which module is causing the problem, I think it's appropriate to take your best guess and pick one or simply go ahead and open an issue in both issue queues. Be clear in your description of the issue that it involves two modules and you are not clear which is causing the problem (maybe both). If opening issues in both queues, I would add a link to the respective issue in the other queue.
If either module maintainer can verify the the problem is not with their module, they can easily close the issue and no harm is done.
As usual, you are much more likely to get results/help if you are able to provide the clearest and easiest possible step by step guide to reproduce the problem.
https://github.com/backdrop-contrib/rules/issues
https://github.com/backdrop-contrib/userpoints/issues