[
https://issues.apache.org/jira/browse/COMDEV-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190956#comment-17190956
]
Rajkumar Raiyan commented on COMDEV-270:
Thanks for your help
> GSOC 2018 OFBiz
[
https://issues.apache.org/jira/browse/COMDEV-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190955#comment-17190955
]
Rajkumar Raiyan commented on COMDEV-270:
Thanks for your help
> GSOC 2018 OFBiz
Jarek, this is fantastic! Please let me know if I/we can help with this. The
Helm team has written tools to make some of these processes easier, including
steps to preserve former git history, and GitHub Actions for CI (chart testing)
and CD (releasing chart version packages via GitHub release a
Hi,
I am one of the maintainer of the Airflow Chart (stable/airflow at
https://github.com/helm/charts/tree/master/stable/airflow).
Our idea (described in this discussion
https://github.com/apache/airflow/issues/10523) is to copy or host the current
Airflow chart as it is, like a "community mai
Big +1 for doing this within existing ASF infrastructure. Maybe indeed
current SVN publishing a release snapshot + mirroring is the best way.
IMHO such 'released' charts do not have to have commit history at all
(except 'release' commits) - just release 'snapshots' is enough. For all
the other d
Hi,
On Fri, Sep 4, 2020 at 9:22 AM Jarek Potiuk wrote:
> ...I think having ASF "apache/chart" for all "officially released" helm
> charts is the best solution
Sounds like a good idea but please use a more specific name, "charts"
is very generic.
If distributing those Helm charts does not re
I've been thinking a lot and discussing the issues mentioned here (as
in Apache Airflow we had this very case to solve. I would like to extend
what Kamil wrote - and comment on what Apache Airflow uses and some of the
recent discussions we had. I think we had very recently a lot of
discussions abou
