Rename master branches to stable
I think renaming the
master branches to
stable is a good idea, primarily because
stable is more self-explanatory than
master to the average person.
master term has multiple meanings in computer science, such as being a synonym for the primary system in a cluster, or in our case reference to the "golden master" (in terms of mastering releases, the plate used to press vinyl records would be referred to as the "golden master"). This ambiguity can lead to confusion.
If we do this, then
stable branch will refer to the newest maintained stable branch. Other maintained branches will be on
release/$version, such as
release/1.0 with the individual branches used to compose the release branch being
release/1.0.6 and so on.
And so with Pleroma 1.1 going out the door, we would have three branches in play:
stable(presently equivalent to
release/1.0(I intend to provide security updates for another 6 month period on 1.0)