RFR: Filing bug, ProblemListing, Backing out [v6]

[Alan Bateman]

On Thu, 23 Jul 2020 18:26:53 GMT, Igor Ignatyev <iignatyev at openjdk.org> wrote:

>>> Filing a Bug - are you going to say anything about checking if the issue exists in the main line, esp. with
>>> reproducible issues? Also what about advice on attaching a reproducer if possible?
>> 
>> Good suggestion! I have added both.
>> 
>>> "ProblemListing or `@ignore`-ing a Test". The ProblemList.txt files are jtreg exclude list. Can this section be renamed
>>> to "How to exclude tests"? I don't think we've used "@ignore" for long time and might it simpler to just not mention it.
>> 
>> I agree with changing the header of this section, and I do like "How to"-sections, but currently the guide doesn't have
>> this style so I suggest simply "Excluding a test".
>> As for the usage of `@ignore`; the keyword is used in ~100 tests, about a third in each of hotspot, jdk, and langtools,
>> so it's clearly used. I've added a few words to say that this is a less common use case, but I think the description as
>> such should remain.
>
>> As for the usage of `@ignore`; the keyword is used in ~100 tests, about a third in each of hotspot, jdk, and langtools,
>> so it's clearly used. I've added a few words to say that this is a less common use case, but I think the description as
>> such should remain.
> 
> for the record, the discussion has continued on [the mailing
> list](https://mail.openjdk.java.net/pipermail/guide-dev/2020-July/000225.html) (but due to some reasons hasn't been
> bridged to this PR), [8249618](https://bugs.openjdk.java.net/browse/JDK-8249618) has been filed to normalize/clean up
> usage of `@ignore` vs ProblemList.

One other comment on this is that "Filing a Bug" asks for labels to be added. Is there anywhere to link to that
describes these labels? If not, then maybe this section could at least include a sentence about the "regression" label
as it's a really useful indication that the reporter thinks there is a regression. If possible, the reporter should try
to narrow down which release or build the regression first appeared as this can save a lot of time when looking at a
bug report.

-------------

PR: https://git.openjdk.java.net/guide/pull/21