So I agree the branch is basically useless now, but I do see a reason to keep it around for now:
There may be active PRs that are still targeting this branch (though Madicken did a great job at reaiming them to master) or worse: people could have local development branches based of this one that they intend to open a PR.
The migration path is pretty clear in both cases: those branches should just be rebased onto master.
However, not every contributor is very confortable with git in general so I don’t think it’s a good idea to make the path any more confusing to them.
Instead of deleting the branch, we might just want to protect it to prevent someone accidentally push to it.
I may be overly cautious, I don’t know. In any case, this the only reason I can see against deletion.
I don't see a reason to keep it around, but I'm also not sure I understand the subtleties that we may run into if we remove it.
Congratulations to the team on merging yt-4.0 into the main dev branch of the repo a couple months ago!
I noticed that the yt-4.0 branch is still hanging around the main yt repo. Unless there is a good reason that it's sticking around, I propose we delete it so as to not confuse users who might checkout that branch, when it's no longer being updated since it was merged with the master branch.
I'm happy to do this, but I didn't want to take unilateral action if there was a good reason others were keeping it on, and due to the way github works, I don't think there is a way to PR a branch deletion. One just has to do it from the web interface (or push a local change).
Is there any reason to keep the yt-4.0 branch around now that it's merged with the master branch? If not, I'll delete it in the next few days.
California Institute of Technology
yt-dev mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Member address: firstname.lastname@example.org