![]() The maintainers may approve with jdk17u-critical-yes, defer to jdk17u-dev or reject altogether. More minor bugs and new features should go in the next release being developed in jdk17u-dev. As the name of this tag suggests, this process is intended for fixes such as major regressions that must make the release. If a change needs to be pushed to a release in rampdown, push approval can still be requested using the jdk17u-critical-request label. The master jdk17u repository contains the latest version of that release, while the jdk17u-dev repository is used to start work on the next release. If and only if the fix gets approved, it may be pushed to the jdk17u-dev repository. Approved fixes show up in this JBS filter (login required).ĭuring the later stages of a release cycle, the release enters rampdown. Outstanding approvals can be monitored here. The maintainers will either approve by setting jdk17u-fix-yes or reject by setting jdk17u-fix-no. Push approval for a fix is requested by setting the jdk17u-fix-request label on the original JBS bug. If the backport requires more than just cosmetic changes (file location changes, copyright header updates) to apply to the 17u repository, it should first be submitted for review. Please ask on the jdk-updates mailing list mailing list if you are in any doubt about whether your proposed backport might qualify. However, if there is an enhancement that provides substantial benefit to OpenJDK 17u users and it is of low risk, we will consider it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |