Automate Update Of JDK/JRE spec files etc during a release.
Open
enhancement
- Dominant language
- Jinja
- Stars
- 168
- Forks
- 77
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 12
Description
During a release cycle, a single PR per Java version is raised to update various spec files and changelogs etc with new filenames, version numbers and checksums, as shown in the linked PRs.
#701 / #700 / #699 / #698
This process could be improved with the use of automation.
Contributor guide
Research direction
Review the linked release PRs (#701, #700, #699, and #698) to identify the spec files, changelogs, filenames, version numbers, and checksums updated for each Java version. Define the release automation scope and consider the work complete when one release process can produce the required updates consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100