You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose to create a branch default, make it the default branch, and after safely merging from master remove the master branch for good. We have no slave branches in the repo, so, no master needed, I guess. Also, We rarely have the luck, to find really canonical names in software and standards development 😉 Other name candidates to me sound weird. For example:
latest as well as main are bad choices for the default branch in most cases. The docker harbor choice gives many users the impression of latest and greatest, but sometimes it is only latest and producers can label whatever they like latest in the docker docks. The term main is also often misleading, as we tend to not offer subsidiaries.
The 8 forks are mostly from TC members and also their owners are easy to contact, to avoid any bad mood in our neighborhood when executing this change.
The text was updated successfully, but these errors were encountered:
sthagen
changed the title
Now for something completely different: default branch rename to ..l default
Now for something completely different: default branch rename to ... default
Jul 4, 2020
I propose to create a branch
default
, make it the default branch, and after safely merging from master remove themaster
branch for good. We have noslave
branches in the repo, so, nomaster
needed, I guess. Also, We rarely have the luck, to find really canonical names in software and standards development 😉 Other name candidates to me sound weird. For example:The 8 forks are mostly from TC members and also their owners are easy to contact, to avoid any bad mood in our neighborhood when executing this change.
The text was updated successfully, but these errors were encountered: