8u/11u repo access and Jira changes

Andrew Hughes gnu.andrew at redhat.com
Tue Feb 26 21:10:47 UTC 2019

On Tue, 26 Feb 2019 at 19:47, Aleksey Shipilev <shade at redhat.com> wrote:


> I have no energy to fight it, though. If you want to keep stable tree pushable for everyone, fine. I
> do reserve the right to say "told you so" every time the "Oops, I pushed to the wrong tree, sorry"
> thread appears, requiring the backout, cleaning up the hgupdater mess in JIRA (I don't even want to
> think how backouts work with backports...), and perhaps invalidating the testing done for the stable
> release (which are also time-sensitive, tick-tock...) ;)
> -Aleksey

Yeah, I really have no energy to argue about this further either, and
I can see both sides;
I've worked on projects, like aph, where the release branch is only
socially restricted, and it works,
but having it done technically does add a bit of peace of mind to
those of us trying to cut releases.

The questions I really need answers to are:

1. Who is going to push from jdk8u-dev -> jdk8u?

2. What is the frequency of these pushes going to be?

3. What testing is going to be performed prior to these pushes?

I'd prefer regular pushes with tags, because that would help us
downstream (aarch64-port/jdk8u-shenandoah,
shenandoah/jdk11) in being able to integrate changes more frequently.
Under Oracle, we've had to do that
at GA time only.

Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Web Site: http://fuseyism.com
Twitter: https://twitter.com/gnu_andrew_java
PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222

More information about the jdk8u-dev mailing list