[
https://issues.apache.org/jira/browse/HADOOP-19605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041419#comment-18041419
]
ASF GitHub Bot commented on HADOOP-19605:
-----------------------------------------
slfan1989 commented on PR #8078:
URL: https://github.com/apache/hadoop/pull/8078#issuecomment-3590851003
> > > disable debian_10 on Jenkins pipeline (broken due to APT repo sunset)
> >
> >
> > If you think this is reasonable, why force the upgrade to Debian 11 on
the trunk?
> > > centos_8 also keeps working, I tested it manually
> >
> >
> > As with the previous question, why push for an upgrade to RockLinux 8?
>
> First of all, I suppose upgrading the building OS, e.g., Debian from 10 to
11, is kind of a riskier change than a normal dependency upgrade (e.g.,
protobuf, jackson), for those changes, trunk should move forward, but feature
branches should stay at the cut point. I think this is a common policy.
Branch-3.4 and trunk are similar in terms of compilation, so they should
follow the same strategy for support. If we decide to end CentOS 7 support in
trunk and upgrade CentOS 8 to RockLinux 8 and Debian 10 to Debian 11, the same
approach should be applied to branch-3.4. There should be no differential
treatment, as the differences are minimal.
> Upgrade Protobuf 3.25.5 for docker images
> -----------------------------------------
>
> Key: HADOOP-19605
> URL: https://issues.apache.org/jira/browse/HADOOP-19605
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.4.2
> Reporter: Cheng Pan
> Assignee: Cheng Pan
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> HADOOP-19289 upgraded protobuf-java 3.25.5, we should use same version for
> protobuf installed in docker images.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
