[
https://issues.apache.org/jira/browse/HADOOP-18721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718582#comment-17718582
]
Ayush Saxena commented on HADOOP-18721:
---------------------------------------
Changed the fix version, thirdparty commits follow different versions.
We have an automated build now for thirdparty commits which deploys the
snapshot version immediately post a commit is made to that repo.
https://ci-hadoop.apache.org/view/Hadoop/job/Hadoop-thirdparty-trunk-Commit/
So, for this commit also we have a 1.2.0-Snapshot deployed. In the past we do
have a PR with the snapshot version raised to trunk, to ensure there aren't any
failures. Did the same with last guava upgrade & the protobuf as well.
Good to follow that here as well, and avoid any surprises post release or
during release vote
> Upgrade guava in hadoop-thirdparty to 31.1-jre
> ----------------------------------------------
>
> Key: HADOOP-18721
> URL: https://issues.apache.org/jira/browse/HADOOP-18721
> Project: Hadoop Common
> Issue Type: Improvement
> Components: hadoop-thirdparty
> Affects Versions: 3.4.0
> Reporter: D M Murali Krishna Reddy
> Assignee: D M Murali Krishna Reddy
> Priority: Major
> Labels: pull-request-available
> Fix For: thirdparty-1.2.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Upgrade guava in hadoop-thirdparty to 31.1-jre to be in sync with the
> downstream project Tez
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
