This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
Issues lifecycle in CONTRIBUTING.md does not reflect current reality #874
Labels
Milestone
Comments
mcwumbly
added
area/repo maintenance
area/docs
kind/bug
mcwumbly
added a commit
to mcwumbly/tanzu-framework
that referenced
this issue
Oct 20, 2021
Related issue: vmware-tanzu#874
mcwumbly
added a commit
that referenced
this issue
Oct 20, 2021
Once a pull request is opened and the review process begins, it is not clear what is needed in order to get the pull request merged. At a high level, we want to try to make the following clear for contributors: - What is the next step towards getting this PR merged? - What's the status of that next step? - Is there anything I can/should do to help make that happen? In doing so, the process aims to clarify the following: - Who is responsible for _reviewing_ my pull requests? - Who is responsible for _approving_ pull requests? - Who is responsible for _merging_ pull requests? - What should I do if it seems like my pull request has gotten "lost in the mix"? How should I determine whether any further action is needed on my part? This is a starting point for documenting a process that we can follow and then further improve. Related issues: - #874 - #844
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug description
This current text in CONTRIBUTING.md does not seem to accurately reflect how we currently do things:
From what I see, we do not label issues as
in-progress, and issues are closed as soon as related changes are merged - they are not kept open until the next release.I'm not sure what the preferred way is to address this in the short term. Maybe we should just delete that whole section? Or is there something valuable worth capturing here?
The text was updated successfully, but these errors were encountered: