Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eliminate need for publish-26-release.yaml #171

Open
bstansberry opened this issue Jan 25, 2023 · 0 comments
Open

Eliminate need for publish-26-release.yaml #171

bstansberry opened this issue Jan 25, 2023 · 0 comments

Comments

@bstansberry
Copy link
Contributor

As discussed at https://github.com/jboss-dockerfiles/wildfly/pull/170/files#r1086726562 consider doing and perhaps do something more sophisticated than the #169 fix. I say 'consider' because it's not at all obvious that improving it is cost effective.

The essence of the #169 problem is there is a particular release stream that can be 'latest' and all other streams cannot. And what stream is the 'latest' is evolves over time. So either a clean algorithm for calculating the 'latest' would be necessary, or we update the yaml to change a constant when it changes.

A further twist is which JDK versions are appropriate can vary based on the release stream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant