| Summary: | Update Java OpenJDK to version 11 (LTS) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | Java Stack Maintainers <java> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | guichard.adrien, mageia, mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | java-1.8.0-openjdk | CVE: | |
| Status comment: | |||
| Attachments: | Version 9 spec file from openmandriva | ||
|
Description
Kristoffer Grundström
2019-07-02 01:55:16 CEST
Created attachment 11140 [details]
Version 9 spec file from openmandriva
Marja Van Waes
2019-07-02 17:22:51 CEST
Assignee:
bugsquad =>
java we won't use openmandriva spec file but fedora one. In any case we shouldn't update to OpenJDK 9 which is already EOL since March 2018... When we upgrade, it should be to the latest LTS OpenJDK 11. Summary:
Update java-1.8.0-openjdk to version 9 =>
Update Java OpenJDK to version 11 (LTS) Is it possible to backport Java OpenJDK 11 (LTS) to Mageia 7, as an alternative package ? I notice huge performance improvements in our application, and no visible regressions (Grails 4 application). It will allow developers to have the same version than the one used on our deployment servers (which will be upgraded to Fedora 30). Thanks! CC:
(none) =>
guichard.adrien At least I think it is a big mistake, not to have a more up-to-date java package than version 8. Version 12 already exists, and we still ship 8?? CC:
(none) =>
mageia
Marc Krämer
2019-08-05 14:12:46 CEST
Priority:
Normal =>
High It's not a mistake. Updating to 11 would have required rebuilding the whole Java stack with 11, and fixing any errors that presented. We had to go with the version that we were ready to support for Mageia 7. It would have been nice to go with 11, but we didn't have the time or manpower to do that. Obviously we will eventually update Cauldron to 11, so this bug is not necessary. As for a backport, we'd need to have the manpower to support it, so... Status:
NEW =>
RESOLVED |