-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of "RTBC" in Core Issue Queue #13
Comments
I dont agree that we can have both labels on an issue. If it is RTBC (in either interpretation of the acronym) it means it ready, which can only mean that the code is satisfactory and its been tested. I believe how I've been viewing this (and I suspect most others) is that we have two intermediate labels:
But RTBC means I've done both. |
I agree, except in my understanding testing and reviewing doesn't have to be done by the same person. |
Agreed. |
I am not sure if this is the best place for this discussion, but I'll give it a try.
I'd like more clarity on how folks are using the "RTBC" label in the core issue queue and then suggest that we update the "Contribution" page to be a bit more clear.
I've seen some issues that are marked both "PR-Ready To Be Committed" and "PR - Needs Testing".
This seems contradictory to me, since how can something be ready to be committed if it still needs testing. I've always assumed the following:
Neither of the following sources of documentation (both of which talk about the RTBC label) are completely clear on this issue.
https://docs.backdropcms.org/documentation/contribute-to-backdrop-core
https://backdropcms.org/user-guide/adding-labels-issues
The second source of documentation does say:
pr - ready to be committed = Someone who did not create the pull request will need to test and review the work. If this person approves of the pull request, they can then add this label.
This seems to imply that testing and code review are both complete.The text was updated successfully, but these errors were encountered: