Retiring master
Jul. 28th, 2014 01:42 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
We have two main branches in the Dreamwidth repositories: master and develop.
master
was intended to be used but... never really got any love.
So here's what I propose: remove all the instructions in our documentation which mention master
, and just have 'develop`.
Since develop
is where all work goes, nothing in the dev workflow will officially change. But occasionally we have accidents where master
gets merged into develop
instead of the other way around, or someone finds themselves on master
when they should be on develop
instead -- and removing any mention of master
from our instructions should prevent that from ever happening again.
As for what will happen to master
... we never actually used it, and at this point ingrained habits for develop
+ all setups old and new assume develop
, so I suggest we continue not using master
the way we currently do.