From: flo@... Date: 2021-04-29T17:00:59+00:00 Subject: [ruby-core:103661] [Ruby master Misc#17828] Deprecate use of master and slave Issue #17828 has been updated by Skade (Florian Gilcher). For reference, the Rust project decided to switch to `main` because it is the tools default and running on defaults has value. Still, it's doing so on a relaxed timeline: https://internals.rust-lang.org/t/changing-the-default-branch-from-master-to-main/14520/6 The `main` problem here is making sure that tooling that encodes `master` as a name (instead of rev-parsing HEAD and checking it out) may break. This may include build pipelines of users out there building software. As @duerst lines out, this has already been done by adding a symbolic-ref. We did not find rehashing discussions useful, considering that upstream git has had that discussion and opted for a new default. ---------------------------------------- Misc #17828: Deprecate use of master and slave https://bugs.ruby-lang.org/issues/17828#change-91756 * Author: yyoshida.at.work@gmail.com (Yasuhiro Yoshida) * Status: Open * Priority: Normal ---------------------------------------- In light of organizations like Basecamp and GitHub refraining from using words like "master" and "slave," it may be a good time for Ruby Core team to follow the practices. I also feel that this issue has been discussed before, and there may already be plans in place as it's a nice thing to do and there is a lot to cover that may require concerted efforts by the whole team. It would be nice if I could learn them and maybe contribute to the task. For now, I am thinking maybe I can start working on most of the documentations, comments, and even tests that have the terminology but wouldn't affect the code that is run in production. -- https://bugs.ruby-lang.org/ Unsubscribe: