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

[calnan]

On Tue, 9 May 2023 01:55:07 GMT, Joe Darcy <darcy at openjdk.org> wrote:

>> Have left the text as-is for the moment - let me know if you feel changes are needed
>
>> 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.
> 
> Right; if something didn't "work" in a shipped release, it can be a bug, but *not* a regression.

updated the definition of a regression to be:

A bug is a regression when behavior has _incorrectly_ changed from a previous release.

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

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