8u/11u repo access and Jira changes
aph at redhat.com
Tue Feb 26 18:46:57 UTC 2019
On 2/26/19 6:30 PM, Aleksey Shipilev wrote:
> On 2/26/19 7:21 PM, Andrew Haley wrote:
>> https://hg.openjdk.java.net/jdk8u/jdk8u is now writable by all JDK 8u
>> Reviewers and Committers. HOWEVER, don't commit anything to
>> it. Instead, commit to jdk8u-dev.
> Wait, can't we limit the push privileges to jdk8u/jdk8u to avoid
We could, but...
> I would prefer computers do things for us for a change. No matter
> how we try to follow the processes, mistakes would happen, and we
> better catch them mechanically. Ditto for jdk-updates/jdk11u.
As I said in
The problem is that we've been conflating two roles in the
"maintainer". One is someone whose role is essentially judgmental:
they decide whether a patch is suitable for a particular
release. The other role is integrative: they merge a patch into a
release branch and make sure the result works by testing it. These
two roles are not the same thing, and require different skills.
We are likely to encounter scaling problems as we work on the
updates projects and we will do ourselves no favours by creating
bottlenecks to efficient parallel working. A mature updates project
would allow many people, with different skills, to work together on
a release branch. Not all of these people would have the authority
(or even the desire) to approve patches.
We have a group responsible for managing the release branch, and these
could be the people with commit access to that tree. But I
don't want to restrict that group necessarily to be the maintainers.
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the jdk8u-dev