You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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 guess1.29.1
or1.30.0
. My question is, if this PR could be also included in1.28.x
? Currently it's1.28.0
but if it's possible to bump it to1.28.1
with this PR?The text was updated successfully, but these errors were encountered: