RFR: Updates to the JBS section of the OpenJDK Dev Guide [v2]

[Jesper Wilhelmsson]

On Tue, 21 Mar 2023 05:33:58 GMT, David Holmes <dholmes at openjdk.org> wrote:

>> calnan has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   Rewrite of the Issue Type table, minor updates, and changes for formatting consistency across the file
>
> src/guide/jbs-jdk-bug-system.md line 192:
> 
>> 190:     1. Only one fixversion should ever be set, if the issue is to be fixed in additional releases then a separate backport must be created (See Working with backports in JBS).  There are exceptions to this rule for: CSRs; and, Release Notes.
>> 191: 1. make sure the bug has all the required labels – JBS Label Dictionary
>> 192:     1. bugs that are new in the current release: 'regression'
> 
> This is tricky. We don't generally use "regression" during active development of the current release, it tends to be used mainly for issues that are found after a release has been released e.g. if we release JDK 19 and then a bug report comes in because something that worked in 18 now doesn't, then it is a regression in 19. But if we are in the process of developing a release and we have added some new thing and then we find a bug in that then we don't mark that as a regression. And a lot of the time if we introduce a bug "by mistake" we don't tend to mark it as a regression.

We probably should be better at marking that last category as regressions though since there are special rules around deferring those.

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

PR Review Comment: https://git.openjdk.org/guide/pull/100#discussion_r1186441962