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

Minor release update contributions should be easier #352

Closed
mi-hol opened this issue Aug 18, 2021 · 5 comments
Closed

Minor release update contributions should be easier #352

mi-hol opened this issue Aug 18, 2021 · 5 comments
Labels
enhancement New feature or request

Comments

@mi-hol
Copy link

mi-hol commented Aug 18, 2021

Is your feature request related to a problem? Please describe.
Many potential contributors are looking for a simple way to add or update version & EOL for an existing product.
My example is Java 8u302.
contributing.md doesn't mention this "simple" use case yet.
Forking of repo and modification of a markdown page is creating a hurdle, that turns out to be too high for many potential contributors

Describe the solution you'd like
a database and web page for these simple manual updates would be a great solution

Describe alternatives you've considered
a data import via spreadsheet, but error handling creates too much of a hassle for potential contributors

Additional context

@welcome
Copy link

welcome bot commented Aug 18, 2021

Thanks for opening your first issue here! Be sure to follow the issue template!

@captn3m0
Copy link
Member

Thanks, this is something I've also wanted to improve. Perhaps having a guide with screenshots of a sample edit would help? Something that highlights all the clicks and possible edits?

A database approach is something I'm not very keen on. Having the source on GitHub easily makes it very easy to hack on. There are short-comings of the YAML approach for sure (including ease of contribution), but it hasn't held us back much while giving us a good structure.

Aside: For patch/minor updates to the latest release - there is a WIP effort (#322) to automatically update the same. It doesn't apply to Java sadly, because OpenJDK maintains release information across multiple git repositories. So long-term, these minor PRs for updating latest releases shouldn't be needed for most products.

@captn3m0 captn3m0 added the enhancement New feature or request label Aug 18, 2021
@mi-hol
Copy link
Author

mi-hol commented Aug 19, 2021

Aside: For patch/minor updates to the latest release - there is a WIP effort (#322) to automatically update the same.

Great to see this approach for open source software being worked on, but how would that apply to closed source software?

@captn3m0
Copy link
Member

It depends - if the release information is available somewhere, we can always scrape it.

This attempt targets git/github sources, but as an example - we already scrape GKE version information using Google Cloud APIs (#314).

Planning to use this for Java for eg.

@captn3m0 captn3m0 changed the title clarify how a new version & EOL can be updated for an existing product Minor release update contributions should be easier Aug 19, 2021
@captn3m0
Copy link
Member

With our automation, minor update contributions are rarely needed now for most of the products. Going to close this.

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

No branches or pull requests

2 participants