[
https://issues.apache.org/jira/browse/HADOOP-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848668#comment-16848668
]
Elek, Marton commented on HADOOP-16092:
---------------------------------------
Thank you very much the answer [~eyang].
1. Yes, I would like to create a convenience packaging to the already released
hadoop 2.7.3 It doesn't involve any build step, this is just about to package
the existing voted and released artifacts. No custom build is here just
packaging (this is somewhat similar to create a deb package by bigtop)
2. I think you may misunderstand my lines. Imagine that we create ozone:0.3.0
based on centos image. Centos base image may be updated in case of a security
issue. In this case I suggest to update the centos but not the Ozone in
ozone:0.3.0 image.
3. AFAIK the official release artifact is the source distribution. Can't see
any problem if convenience packaging is created after the announcement. You can
also check the 0.3.0. It also worked well (without your complain). Or is it a
problem to publish the staged maven repository after the announcement?
> Move the source of hadoop/ozone containers to the same repository
> -----------------------------------------------------------------
>
> Key: HADOOP-16092
> URL: https://issues.apache.org/jira/browse/HADOOP-16092
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Elek, Marton
> Assignee: Gabor Bota
> Priority: Major
>
> This is proposed by [~eyang] in
> [this|https://lists.apache.org/thread.html/33ac54bdeacb4beb023ebd452464603aaffa095bd104cb43c22f484e@%3Chdfs-dev.hadoop.apache.org%3E]
> mailing thread.
> bq. Hadoop community can decide what is best for Hadoop. My preference is to
> remove ozone from source tree naming, if Ozone is intended to be subproject
> of Hadoop for long period of time. This enables Hadoop community to host
> docker images for various subproject without having to check out several
> source tree to trigger a grand build
> As of now the source of hadoop docker images are stored in the hadoop git
> repository (docker-* branches) for hadoop and in hadoop-docker-ozone git
> repository for ozone (all branches).
> As it's discussed in HDDS-851 the biggest challenge to solve here is the
> mapping between git branches and dockerhub tags. It's not possible to use the
> captured part of a github branch.
> For example it's not possible to define a rule to build all the ozone-(.*)
> branches and use a tag $1 for it. Without this support we need to create a
> new mapping for all the releases manually (with the help of the INFRA).
> Note: HADOOP-16091 can solve this problem as it doesn't require branch
> mapping any more.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]