Here's my proposal for how we handle cleaning up the branches as part of changing the branching model.
1. If the branch is merged, delete it.
1. If the branch is for an unmerged pull request that is actively being developed:
- Have the original submitter fork the repository and make a new PR from that branch in the fork.
- Delete the branch in the upstream.
- Reference the original PR from the new one so discussion is linked.
- Close the original PR.
1. If the PR is for an unmerged PR that has not seen activity for some time:
- Close the PR.
- Ask the submitter to make a fork and do as for active PRs, above.
- Schedule the branch for deletion in one month.
1. If the branch is not linked to a PR but is actively being developed:
- Ask the person who is working on it to fork and work on the branch in their fork, then do a PR as per the new development process.
- Delete the branch once the fork has been created.
1. If the branch is not linked to a PR and is not actively being developed, delete it. If we really want it the history will still be there so we can resurrect it later.
Please provide comments or alternative proposals!
---
[Visit Topic](
https://discourse.ros.org/t/1-12-development-timeline/8166/2) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)