<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Hi OpenJDK Developers,</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">There are a large number of issues in JBS (14,600+) that are currently in a state that violates the OpenJDK process for how issues should be closed. We intend to clean this up by performing a bulk
update of these issues. No emails will be sent out from JBS as is usually the case when an issue is updated but you may still notice this update if you look at when the issues was most recently updated.</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">If you run tools that monitor JBS activity or rely on the last updated date in issues, please be aware that this will happen over the next week.</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">In short what this is all about is that issues that are closed with resolutions Duplicate, Won't Fix, Cannot Reproduce, Not an Issue, External, Migrated, and Withdrawn should always go directly to
Closed - they should never be Resolved. But since JBS allows it of course it will happen every now and then. We are currently investigating if we can make it so that these resolutions can't be moved to Resolved.</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">There is no change in the process involved here, just a cleanup to make existing issues follow the already existing process. The process is described here: </span><a href="https://openjdk.org/guide/#resolving-or-closing-an-issue">https://openjdk.org/guide/#resolving-or-closing-an-issue</a><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">As this is needed due to the lack of tooling to help us follow the process, I want to take this opportunity to remind everyone about the OpenJDK Developers' Guide (</span><a href="https://openjdk.org/guide">https://openjdk.org/guide</a><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">).
The Guide is a collection of guidelines for how to work in the OpenJDK project. It is assumed that every OpenJDK Developer has read through this document and understands how to work with our various tools and processes. Since the guide is continuously updated
and has grown significantly over the last couple of years, this might be a good time to go back and look at what has changed since you looked at it the last time.</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Best regards,</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">
<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">/Jesper</span>
<div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br>
</span></div>
</body>
</html>