[
https://issues.apache.org/jira/browse/FLINK-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164393#comment-17164393
]
Robert Metzger commented on FLINK-16260:
----------------------------------------
Why would we need to enrich the architecture from the
generate-stackbrew-library.sh script? can't we collect the architecture in the
"dev-X" branch, when we are generating the "stackbrew.entry" file?
My suggestion is: The contract between the "dev-X" branches and "master" is
that they produce a valid "stackbrew.entry" file for
generate-stackbrew-library.sh to consume. How the "dev-X" branches generate
this file is up to them and it could be potentially different between versions.
I fear that adding the "latest" tag is not elegant to add in my approach.
I don't know the scripts well enough to decide whether we need the "meta-data"
file or not. But there would be no harm in having a "meta-data" file to assist
the generation of the final "stackbrew.entry" file.
> Add docker images based on Java 11
> ----------------------------------
>
> Key: FLINK-16260
> URL: https://issues.apache.org/jira/browse/FLINK-16260
> Project: Flink
> Issue Type: New Feature
> Components: Dockerfiles
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Since 1.10.0 supports Java 11, we can add a version of the docker image based
> on Java 11
> Feature [requested in our old issue
> tracker|https://github.com/docker-flink/docker-flink/issues/97] and moved here
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
