RFR: Section about the release process [v2]

[Jesper Wilhelmsson]

On Thu, 12 Aug 2021 00:41:51 GMT, Stuart Marks <smarks at openjdk.org> wrote:

>> This is the way it works. I forward port all changes from JDK 17 to mainline, and if a change is not for mainline it must be backed out. I added a paragraph with your example to clarify the JBS part.
>
> OK. If this is the way it really works, then clearly that reality needs to be documented. I'm a bit surprised about this; on the other hand, I thought of several alternatives, but they're either unworkable or more complicated and don't offer any advantages. This is probably a pretty rare case, so maybe the workflow is fine as it stands.
> 
> The filing-two-bugs material looks reasonable. I might strengthen it to say something like the following.
> 
> « As soon as you know that there is a fix that needs to go into the stabilization fork but not the mainline, you should do the following: file a bug JDK-yyy to cover the backout work, link it to JDK-xxx, set its Fix Version to the next release, add a comment describing the situation, and set the priority to be relatively high (e.g., P3). Then, you have to wait until the JDK-xxx fix is forward ported to the mainline before actually fixing JDK-yyy. Making these settings in JDK-yyy will help ensure that it won't be missed. »

I added your text, but as a list.

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

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