RFR: Section on backporting [v6]

[Andrew John Hughes]

On Wed, 1 Dec 2021 14:01:35 GMT, Goetz Lindenmaier <goetz at openjdk.org> wrote:

>> Jesper Wilhelmsson has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   Update src/index.md
>>   
>>   Co-authored-by: Andrew Haley <aph-open at littlepinkcloud.com>
>
> src/index.md line 1501:
> 
>> 1499: 
>> 1500: In order to be allowed to push a change to one of the OpenJDK Update Release repositories, an approval is required. The [official process for how to request push approval for a backport](https://openjdk.java.net/projects/jdk-updates/approval.html) describes in detail how to work with JBS when requesting approvals. In short, there's a label `jdk<release>u-fix-request` that should be added to the main JBS issue. Also put a motivation as to why the issue needs to be backported as a comment in the main issue. Once the label and motivation has been added, wait for the maintainers of the release to approve your request. The approval will be indicated with a label, `jdk<release>u-fix-yes`, added to the main issue.
>> 1501: 
> 
> Hi,
> I would propose to differ the development and release
> repositories most update projects use (like jdk11u-dev and jdk11u).
> 
> In this case, in the first sentence, it should say 
> "... OpenJDK Update **Development** repositories ..."
> 
> and at the end you could add
>   If an update is in rampdown in the Release repository, 
>   urgent fixes need to be approved with
>   `jdk<release>u-critical-request` / `jdk<release>u-critical-yes`.
> 
> If you want to keep it short, omitting this is ok.  But this is 
> also missing on the "JDK Updates: Requesting push approval for fixes"
> wiki page referred to from here.

+1

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

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