<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Hi Tom,<br>
<br>
Your interest seems to be more in the libraries area, so redirecting
this conversation to <a class="moz-txt-link-abbreviated" href="mailto:core-lib-dev@openjdk.java.net">core-lib-dev@openjdk.java.net</a>.<br>
<br>
There is quite a complete OpenJDK Developers Guide that describes
the process and guidance.<br>
<p><span><a href="https://openjdk.org/guide/" data-ved="2ahUKEwj-0MjGtbuJAxU5NlkFHeluDtMQFnoECB0QAQ" data-sb="/url?sa=t&source=web&rct=j&opi=89978449&url=https://openjdk.org/guide/&ved=2ahUKEwj-0MjGtbuJAxU5NlkFHeluDtMQFnoECB0QAQ&usg=AOvVaw0aF_F9ZkwQdxuYkClm0V4B">
<h3 class="LC20lb MBeuO DKV0Md"><span style="font-weight: normal;">The OpenJDK Developers' Guide</span></h3>
</a></span></p>
There is already quite a bit of process and discussions of process
fit into the mail alias for the DevGuide:<br>
<table width="100%" border="0">
<tbody>
<tr>
<td><a href="https://mail.openjdk.org/mailman/listinfo/guide-dev"><strong>guide-dev</strong></a></td>
<td>Technical discussion related to the Developers' Guide
Project</td>
</tr>
<tr bgcolor="#dddddd">
<td><a href="https://mail.openjdk.org/mailman/listinfo/guide-discuss"><strong>guide-discuss</strong></a></td>
<td>General discussion of topics related to the OpenJDK
Developers' Guide</td>
</tr>
</tbody>
</table>
<br>
<span></span>There are separate email aliases for the VM, language,
compiler, and subareas of the libraries.<br>
For all the Mailing Lists see:
<a class="moz-txt-link-freetext" href="https://mail.openjdk.org/mailman/listinfo">https://mail.openjdk.org/mailman/listinfo</a><br>
<br>
Regards, Roger<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/1/24 10:54 AM, Chen Liang wrote:<br>
</div>
<blockquote type="cite" cite="mid:CH3PR10MB76772EFAED5910367368BE30A2562@CH3PR10MB7677.namprd10.prod.outlook.com">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hello Tom,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
There is a standard template for bug reports at <a href="https://bugreport.java.com/bugreport/" id="OWAd916f5de-2f6d-ba67-b5e5-702ed94de785" class="OWAAutoLink moz-txt-link-freetext" moz-do-not-send="true">
https://bugreport.java.com/bugreport/</a>. Unfortunately,
there are many antique bugs in the JBS which are forgotten, so
they may be obsolete (no longer valid) or their reproduction
steps have changed; we cannot do much. Also, you don't always
have to write identical regression tests as in the bug report;
often times you can write simpler cases with professional test
suites like JUnit, and that's at least the trend on the core
libraries side of the JDK.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
You said you want a definition of "done." Where did you see that
term? In the JBS, you should look for bugs with "Resolution"
that is "Unresolved." If you mean for sending patches, we
recommend that when you open a PR, it should be complete with
tests as if it can be immediately merged, so that you don't have
to push more unless public review request changes.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Chen</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b>
jdk-dev <a class="moz-txt-link-rfc2396E" href="mailto:jdk-dev-retn@openjdk.org"><jdk-dev-retn@openjdk.org></a> on behalf of Tom
Mooney <a class="moz-txt-link-rfc2396E" href="mailto:Tom.Mooney@bjss.com"><Tom.Mooney@bjss.com></a><br>
<b>Sent:</b> Friday, November 1, 2024 9:45 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:jdk-dev@openjdk.org">jdk-dev@openjdk.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:jdk-dev@openjdk.org"><jdk-dev@openjdk.org></a><br>
<b>Subject:</b> Using a standard bug report template and a
definition of done</font>
<div> </div>
</div>
<style type="text/css" style="display:none">p
{margin-top:0;
margin-bottom:0}</style>
<div dir="ltr">
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Has the project tried a standardized bug report template
before with supplied test data and exact steps to reproduce
the bug? I feel that this would help contributors very quickly
reproduce the bug exactly as it was originally produced,
possibly write a regression test(s) for it (where applicable)
and be able to get to the business of fixing it as soon as
possible. Plus it could make it easier for new contributors
like me to get started faster. Its just that I've been
browsing new bugs for something to work on and I find it
difficult to be able to confirm when I've actually fixed it
(apart from not seeing the same error messages produced). I
could volunteer such a template it was deemed by the mailing
list as something that would be useful. Perhaps a definition
of done too would be useful so that bug fixers can know when
they are truly done and they could mail the evidence along
with their patches for review giving them a better chance of
getting their contributions accepted. </div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Ta</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Tom</div>
<br>
<p class="x_MsoNormal"><span style="font-size:8.0pt; font-family:"Arial",sans-serif">The
information included in this email and any files transmitted
with it may contain information that is confidential and it
must not be used by, or its contents or attachments copied
or disclosed to, persons other than the intended addressee.
If you have received this email in error, please notify
BJSS. In the absence of written agreement to the contrary
BJSS' relevant standard terms of contract for any work to be
undertaken will apply. Please carry out virus or such other
checks as you consider appropriate in respect of this email.
BJSS does not accept responsibility for any adverse effect
upon your system or data in relation to this email or any
files transmitted with it. BJSS Limited, a company
registered in England and Wales (Company Number 2777575),
VAT Registration Number 613295452, Registered Office
Address, 1 Whitehall Quay, Leeds, LS1 4HR</span></p>
</div>
</blockquote>
<br>
</body>
</html>