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

Release process #14548

Open
dahlinPL opened this issue Jan 13, 2025 · 2 comments
Open

Release process #14548

dahlinPL opened this issue Jan 13, 2025 · 2 comments

Comments

@dahlinPL
Copy link
Contributor

Hi!

I have question about possibility to patch not latest ONE release. Let's suppose that this PR will be successfully merged. As currently latest ONE release is 1.29.0 we can expect it will be included in next release, which be I can guess 1.29.1 or 1.30.0. My question is, if this PR could be also included in 1.28.x? Currently it's 1.28.0 but if it's possible to bump it to 1.28.1 with this PR?

@hseok-oh
Copy link
Contributor

hseok-oh commented Jan 14, 2025

As currently latest ONE release is 1.29.0 we can expect it will be included in next release, which be I can guess 1.29.1 or 1.30.0

Current development version is 1.30.0, so commit in master branch will be included in 1.30.0.

My question is, if this PR could be also included in 1.28.x?

If you want to patch to previous release, you should request to maintainers to release new patch version with your requirement. If maintainers allow requirement, we will decide to release new patch version, then release process will be started.

If we need patch to 1.28.x version, we may add patch commit to release/1.28.0 branch or new release/1.28.1 branch (branch out from release/1.28.0) with version update.

@dahlinPL
Copy link
Contributor Author

@hseok-oh Thank you for your answer. I will left this issue opened to allow us request patch of 1.28.x when #14535 will be (eventually) merged.

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