This obviously will break all the current PR to master branch just because of naming. Is it worth this?
What problems renaming will solve? And why does that suddenly become important? -- ,,,^..^,,, On Wed, Sep 9, 2020 at 6:40 PM Paul Davis <paul.joseph.da...@gmail.com> wrote: > Howdy Folks! > > Words matter. I've just started a thread on merging all of the > FoundationDB work into mainline development and thought this would be > a good time to bring up a separate discussion on renaming our default > branch. > > Personally, I've got a few projects where I used `main` for the > mainline development branch. I find it to be a fairly natural shift > because I tab-complete everything on the command line. I'd be open to > other suggestions but I'm also hoping this doesn't devolve into a > bikeshed on what we end up picking. > > For mechanics, what I'm thinking is that when we finish up the last > rebase of the FoundationDB work that instead of actually pushing the > merge/rebase button we just rename the branch and then change the > default branch on GitHub and close the PR. > > Thoughts? > > Paul >
