Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: change main development branch from dev to master #2548

Open
roji opened this issue Jul 25, 2019 · 2 comments

Comments

@roji
Copy link
Member

commented Jul 25, 2019

@YohDeadfall raised this before - we currently work in dev, and merge releases into master. This is different from the standard at Microsoft where master is the development branch (I might just be biased now that I work for them :)).

Proposal:

  • We create a new branch called "release" into which we merge releases (like master today). It's somewhat important to have this for doc purposes (need to have a branch with the latest released version).
  • master becomes what dev is today
  • dev is deleted

@YohDeadfall @austindrenski any objections?

@roji roji added the discussion label Jul 25, 2019

@austindrenski

This comment has been minimized.

Copy link
Member

commented Jul 25, 2019

So, this?

git branch -m master release
git branch -m dev master

It'll take some getting used to... But if it reduces the context switching burden for you (e.g. easier to multitask between ado.net and npgsql), then no objections here.

@roji

This comment has been minimized.

Copy link
Member Author

commented Jul 25, 2019

So, this?

Pretty much. One issue is that outstanding PRs open against dev will likely be closed when that happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.