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

Use single branch instead of develop/master split. #521

Open
holtgrewe opened this issue Jun 8, 2021 · 2 comments
Open

Use single branch instead of develop/master split. #521

holtgrewe opened this issue Jun 8, 2021 · 2 comments

Comments

@holtgrewe
Copy link
Member

Is your feature request related to a problem? Please describe.
Separating develop and master is not so useful for our project. Also, the default Maven release cycle assumes a single branch only. Releasing requires going to the master branch and then

Describe the solution you'd like
Get rid of the develop branch and use master for development. Releases go to Maven central anyway. While we're at it, we can move away from legacy master to main.

Describe alternatives you've considered
Leave things as they are.

Additional context
N/A

CC @visze @pnrobinson

@pnrobinson
Copy link
Contributor

I agree there is no big advantage in separating develop/master

@holtgrewe holtgrewe added this to the v0.37 milestone Jun 9, 2021
@holtgrewe
Copy link
Member Author

I'm removing the legacy master and develop branchs in favour of the now default main branch.

@holtgrewe holtgrewe removed this from the v0.37 milestone Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants