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

Should the default branch be updated 4.14? #421

Closed
Levi-Armstrong opened this issue Jan 20, 2021 · 4 comments
Closed

Should the default branch be updated 4.14? #421

Levi-Armstrong opened this issue Jan 20, 2021 · 4 comments

Comments

@Levi-Armstrong
Copy link
Member

@christian-rauch Should we change the default branch to 4.14?

@christian-rauch
Copy link
Member

Once #417 is merged (feel free to merge if you are happy with the issues discussed in #417 (comment)) I would always have the default branch track the current state.

This could be done in two ways:

  1. the default branch is changed every time a new release happens (4.14, 4.15, ...),
  2. there could be a devel branch (since master is already taken for the documentation) that keeps track of the current state and branch out every time the API changes (i.e. with every Qt Creator minor release).

Maybe the devel branch option is easier since it does not involve changing the repo settings with every new Qt Creator release. I think the ROS behaviour is similar, in that the branches stay the same until the API breaks.

@Levi-Armstrong
Copy link
Member Author

A devel branch sounds good.

@christian-rauch
Copy link
Member

I went ahead and created the devel branch after the 4.14 merge. Can you @Levi-Armstrong set it as the default?

@Levi-Armstrong
Copy link
Member Author

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants