From: takashikkbn@... Date: 2019-05-22T10:34:42+00:00 Subject: [ruby-core:92783] [Ruby trunk Misc#15843] Make "trunk" a symbolic-ref of "master" on git.ruby-lang.org Issue #15843 has been updated by k0kubun (Takashi Kokubun). Description updated > If you change something, pls tell your schedule and we can check the CI system. Sure. I updated the description. Once I make a symbolic-ref tomorrow, I'll post an email to ruby-core to share the schedule and ask for updating CI system to use master branch. > But, I want to know what do you mean in the term "Out of scope (for a short term)". > What is "short" ? I included a concrete schedule for all related operations in the new description. Because @mame is going to make a big change in ruby-commit-hook check-email.rb in 2020, I'm thinking about making the last operation happen at the similar timing. > I'm negative against the Main part (moving the branch) immediately, which seems a too big change. > Why not making "master" as a symbolic-ref at first? The new schedule adopted your proposal. "making `master` as a symbolic-ref at first" will be done tomorrow as the first step. For "moving the branch", I split the operation to "changing HEAD" and "mv refs/heads/trunk refs/heads/master", and planned to make the former on 2019/7/1 and the latter on 2020/1/1. ---------------------------------------- Misc #15843: Make "trunk" a symbolic-ref of "master" on git.ruby-lang.org https://bugs.ruby-lang.org/issues/15843#change-78148 * Author: k0kubun (Takashi Kokubun) * Status: Open * Priority: Normal * Assignee: ---------------------------------------- ## Background * We're using `trunk` branch as a canonical development branch because it has been mirrored to there by git-svn. * In a usual git repository, a HEAD branch is `master` by default. Using `trunk` instead of `master` is confusing and causes typo on git operations or typing git-related URLs. * We can make an *alias branch* by using symbolic-ref on `git.ruby-lang.org:ruby.git`. We can start using `master` branch without disturbing any `trunk` usage. Why not use it? ## Proposed schedule * 2019 * 5/22: Announce this schedule * 5/23: Make `master` symbolic-ref pointing to `trunk` on git.ruby-lang.org * 5/23~6/30: Ask maintainers of CI (or whatever integrated with the repository) to explicitly use `master` branch instead of `trunk` at ruby-core mailing list. * 7/1: Switch HEAD on git.ruby-lang.org from `trunk` to `master` * 2020 * 1/1: Drop `trunk` branch on git.ruby-lang.org (`mv refs/heads/trunk refs/heads/master` at `/var/git/ruby.git`) -- https://bugs.ruby-lang.org/ Unsubscribe: