Restructuring Branches

[Davidutro]

Problem:
Lots of Branches, lots of overhead to keep them straight, crappy UX for mip authors, etc

Solution:
Eliminate all but the master branch.

Discussion points:

• What does the process look like with one branch?
• ??? add more if you think of any

@CPSTL

[Davidutro]

Re: process

1. MIP authors create a PR at the beginning of RFC as usual, except it's for the master.
2. They perform the updates to the MIP as it passes through RFC there, making active updates to the PR.
3. PR is merged upon approved status

Does this sound reasonable? I am coming at this with totally fresh eyes, so lmk what you think @CPSTL

[Davidutro]

During the 02/02/21 governance domain meeting, Juan, LFW, and Prose all agreed that we can move ahead with deleting the unneeded branches and sticking purely to master and RFC for now. With the plan being to deprecate RFC as well, just having people push to master

[Davidutro]

Problem:
One thing that worries me is dealing with amendments without an RFC branch.
If everything gets pushed to master then approved mips get messed up until the MIP amendments are accepted or rejected.

Solution:
The MIP4c2 would be added to master while the amendments would be submitted as a separate PR, that would be merged when accepted. - LFW

[Davidutro]

I deleted all but the master and RFC branches.

I think we will delete the RFC branch soon as well, just want to think about the process a bit to make sure there isn't anything we're overlooking.

[Davidutro]

This project is done, all branches are gone beside master