You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:38:10 UTC
[jira] [Updated] (HDDS-1566) Move docker image generation from dist
project k8s-* profiles
[ https://issues.apache.org/jira/browse/HDDS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-1566:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> Move docker image generation from dist project k8s-* profiles
> -------------------------------------------------------------
>
> Key: HDDS-1566
> URL: https://issues.apache.org/jira/browse/HDDS-1566
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Eric Yang
> Priority: Major
>
> The current dist module setup is a little messy. There are many things hanging off dist project including tarball generation, docker image generation, and k8s metadata generation. However, maven release will only distribute one of the generated artifacts to maven repository. This can prevent proper release process. It is also useful to move docker image build to a submodule or sibling project for people that does not have k8s system. They can run Ozone cluster on Hadoop 3.1.1+ or docker swarm.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org