Skip to content
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

Open
stpaultim opened this issue Aug 28, 2021 · 3 comments
Open

Use of "RTBC" in Core Issue Queue #13

stpaultim opened this issue Aug 28, 2021 · 3 comments

Comments

@stpaultim
Copy link

stpaultim commented Aug 28, 2021

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:

  1. That you can't really do a final code review until after an issue has been tested. I often see folks do a preliminary code review and add a comment saying that the "Code looks good to me." I usually treat that as a provisional code review that applies only if no problems are found in testing and no changes to the PR.
  2. That an issue is not "RTBC" until it has been both successfully tested and the code reviewed.

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.

@docwilmot
Copy link

docwilmot commented Aug 30, 2021

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:

  • works for me: I've tested it but I havent reviewed the code
  • needs testing: I havent tested it; I may or may not have reviewed the code.

But RTBC means I've done both.

@olafgrabienski
Copy link

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.

@stpaultim
Copy link
Author

except in my understanding testing and reviewing doesn't have to be done by the same person.

Agreed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants