RFD: Draft guidelines for working on jdk8u

[Andrew Haley]

On 2/20/19 12:32 AM, Andrew Hughes wrote:
> On Tue, 19 Feb 2019 at 17:52, Andrew Haley <aph at redhat.com> wrote:
>>
> snip...
> 
>> We have two active trees, hg.openjdk.java.net/jdk8u/jdk8u/ and
>> hg.openjdk.java.net/jdk8u/jdk8u-dev/. jdk8u-dev is always open to all
>> contributors, and that's where everyone should push their patches
>> after maintainer approval. When the time comes for an update release,
>> jdk8u-dev will be copied to jdk8u for testing and stabilization. From
>> that point onwards only critical bug fixes may be applied to jdk8u, at
>> the discretion of the maintainers.
> 
> I think jdk8u-dev -> jdk8u syncs need to be done at more regular intervals
> with jdk8ux-by style tags.

Yes. Once a week has been suggested. So I should fix this para with

>> We have two active trees, hg.openjdk.java.net/jdk8u/jdk8u/ and
>> hg.openjdk.java.net/jdk8u/jdk8u-dev/. jdk8u-dev is always open to all
>> contributors, and that's where everyone should push their patches
>> after maintainer approval.
>> [ Patches pushed to jdk8u-dev will be copied to jdk8u at regular intervals.]
>> When the time comes for an update release,
>> jdk8u-dev will closed for testing and stabilization. From
>> that point onwards only critical bug fixes may be applied to jdk8u, at
>> the discretion of the maintainers.

OK?

> Also, in the spirit of 11u, are we intending to adopt its process of using
> bug labels to request backports rather than e-mails i.e. jdk8u-fix-request? [0]
> 
> [0] https://openjdk.java.net/projects/jdk-updates/approval.html

Yes. I didn't spell it out because it's in that reference:
>> In general we'll use the process in
>> https://openjdk.java.net/projects/jdk-updates/approval.html.

It would be hopelessly confusing to do it differently.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671