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

Question about release process #1053

Closed
josecelano opened this issue Sep 30, 2024 · 3 comments
Closed

Question about release process #1053

josecelano opened this issue Sep 30, 2024 · 3 comments
Assignees
Labels
Installer | Package Distribution to Users Question / Discussion Community Feedback
Milestone

Comments

@josecelano
Copy link
Member

Hi @da2ce7, following the release process what should be the next develop version after v3.0.0-rc.1? v3.0.1, v3.1.0?

@josecelano josecelano added Installer | Package Distribution to Users Question / Discussion Community Feedback labels Sep 30, 2024
@josecelano josecelano added this to the v3.0.0 milestone Sep 30, 2024
@da2ce7
Copy link
Contributor

da2ce7 commented Oct 2, 2024

We create a v3 branch, that will be for bug fixes and new features. We bump the version based upon https://semver.org policy.

If we make a breaking change or start working on the next major version, then we can start using the develop branch again. This time with the v4.0.0-alpha... versioning.

In summary: (my recommendation)

Use the v3 branch while we work improving the v3.x.y series... once we decide to move onto the next major version: we move back to using the develop branch.

@josecelano
Copy link
Member Author

We create a v3 branch, that will be for bug fixes and new features. We bump the version based upon https://semver.org policy.

If we make a breaking change or start working on the next major version, then we can start using the develop branch again. This time with the v4.0.0-alpha... versioning.

In summary: (my recommendation)

Use the v3 branch while we work improving the v3.x.y series... once we decide to move onto the next major version: we move back to using the develop branch.

Hi @da2ce7, OK, then I will follow the release process only until step 7, and create a new v3 branch.

cc @mario-nt

@josecelano
Copy link
Member Author

Hi @da2ce7, we have already merged into develop this PR:

#1058

and the cargo version is version = "3.0.0-develop".

It should have been merged into branch v3, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Installer | Package Distribution to Users Question / Discussion Community Feedback
Projects
None yet
Development

No branches or pull requests

2 participants