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.

Sign up for GitHub

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

Jump to bottom

Branching process Julep #52

Open
simonbyrne opened this issue Aug 13, 2018 · 1 comment
Open

Branching process Julep #52

simonbyrne opened this issue Aug 13, 2018 · 1 comment

Comments

@simonbyrne
Copy link
Contributor

simonbyrne commented Aug 13, 2018 •
edited
Loading

We need to figure out how we're going to handle branching going forward. For the immediate future we plan to keep master as 1.1, but we will need to figure out how we want to handle breaking changes in the long term.

The key questions

  • How to structure our branches?
  • What tooling can we use to minimise the need for manual intervention with handling backports?
  • What should get backported to minor and patch releases?
@oxinabox
Copy link

oxinabox commented Aug 15, 2018 •
edited
Loading

I think we should get rid of master, and just have 1.x-DEV and 2.x-DEV

Mechanical it is no different, but names matter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@simonbyrne @oxinabox