You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
This current text in CONTRIBUTING.md does not seem to accurately reflect how we currently do things:
Issues Lifecycle
Once an issue is labeled with in-progress, a team member has begun
investigating it. We keep in-progress issues open until they have been
resolved and released. Once released, a comment containing release information
will be posted in the issue's thread.
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:
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
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: