Date: Fri, 29 Mar 2024 12:56:05 +0000 (UTC) Message-ID: <184276980.1355.1711716965218@34fc92c9345b> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1354_122363043.1711716965218" ------=_Part_1354_122363043.1711716965218 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
After a new P= roject Lead was not identified and several months of inactivity, the Projec= t was dissolved Apr 2023. Discussion about reinstating a JDK 7 Updates Project ma= y be held on discuss. |
It would be nice if there was a way for OpenJDK 7u Authors, Committers a= nd Reviewers to flag critical fixes that have been integrated into jdk7u-de= v for consideration by the Oracle JDK 7u CPU Release Team for inclusion int= o a CPU release ahead of the release being worked on in jdk7u-dev.
Such a process can be facilitated if one follows the rules outlined belo= w.
An OpenJDK 7u Author, Committer or Reviewer requesting their fix in jdk7=
u-dev to be considered by the Oracle JDK CPU Release Team for CPU integrati=
on SHOULD label the corresponding issue with CPU-critical-request in the JDK Bug System.
If (and only if) approved by the Oracle JDK 7u CPU Release Team the labe=
l will be updated to CPU-critical-approved
.
They will then ensure that the approved fix gets integrated to an upcomi= ng Oracle JDK 7u CPU release.
All relevant updates will be processed via the bug report.
Such bug fix requests should only be made for critical fixes. A guidelin= e is