[
https://issues.apache.org/jira/browse/HADOOP-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854441#comment-16854441
]
Elek, Marton commented on HADOOP-16092:
---------------------------------------
Thank you very much the answer [~eyang]. This issue is created to move some
sources from one branch to an other git repository, but the discussion has been
changed and If I understood well it's not about this jira any more but the
release process of ozone.
I am closing this issue because it seems we can't find any consensus. I am very
sorry but I don't think how is it possible. It seems that we can't agree even
on the fundamental questions if the Ozone is a Hadoop subproject or not. (I
think it is).
bq. Convenience binary for hadoop-runner:latest does not have the same version
number for Ozone 0.4.0 which is not compliant to Apache release policy.
Our binary image is apache/ozone:0.4.0. It has the same version number and in
fact this is just a downstream distribution of the already created convenience
binary.
It seems that you know about multiple problems related to the release process
but not related to this hira. Would you be so kind to create separated issue
for them to get more focused discussion (I suggest to use HDDS project). Thank
you, in advance.
> 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
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
