Move P build from 4.28 based to 4.29 #1325
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@sravanlakkimsetti @MohananRahul Can you please check if the changes are fine. At this point, both Y and P builds are broken. |
jarthana
force-pushed
the
pbuild_update
branch
from
dd11ce6 to
569f16c
Compare
|
I have rewritten the original changes with just the pom changes that change the versions from 4.30.0-SNAPSHOT to 4.29.0-SNAPSHOT. I think it was wrong to reference 4.30 for the patch build. |
|
@rgrunber this might be of interest |
|
@jarthana Do you need this one merged? |
|
PBuild is available from 4_29 maintenance, so this PR is not needed. @jarthana please confirm. |
|
Agree, we already have the required changes in. This is redundant now. Closing this now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am not very sure about all the changes here. All I have done is to update all the build related values to +1 - for e.g., 4.28 to 4.29 and 4.29 to 4.30 and so on. Perhaps we can wait till we have the 4.29 release build and update again, but just wanted to create the PR so we can track it.