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
There has been some debate on the cf-dev mailing list about whether teams should replace "master" with "main" or with some other term. I think we should chose "main" because that is what github changing its default to. By choosing the same default branch name as github this will provide predictability and cohesion between repos.
The text was updated successfully, but these errors were encountered:
I'm in favor of "main" if we believe that it'll be more consistent with other repos.
If consistency seems unattainable, then I'd vote for "release", given the table you helpfully put together above. Let's include that table (with the new name) in https://github.com/cloudfoundry/routing-release#developer-workflow and/or in a new CONTRIBUTING.md while we're at it!
jenspinney
added
the
scheduled
We agree this change makes sense and plan to work on it ourselves at some point.
label
Jul 1, 2020
Current State
We have 3 non-wip branches that we use for routing-release.
Desired State
Why does this matter?
Master/slave terminology has existed for decades and has permeated many aspects of computer science and other fields. It is also extremely racist. We should stop using these terms.
There has been some debate on the cf-dev mailing list about whether teams should replace "master" with "main" or with some other term. I think we should chose "main" because that is what github changing its default to. By choosing the same default branch name as github this will provide predictability and cohesion between repos.
The text was updated successfully, but these errors were encountered: