[11u] Proposal: Switch jdk11u development to Git/Skara with 11.0.13 cycle

[Andrew Hughes]

On 08:38 Fri 12 Feb     , Langer, Christoph wrote:
> Hi Andrew,
> 
> you have valid concerns which I hope we can get sorted out until the proposed 11u switch. Let me answer in detail:
> 
> > I have still not seen any answer to my question of how a bulk update is
> > pushed for the CPU.
> 
> I think generally this is kind of answered. For the 11u <-> 11u-dev merges we can use a facility called "Merge PR", something like people used to merge jdk16 back into jdk [0].
> Although I've not yet done it myself and will need to talk to Skara folks to get it explained better, I think this is what we can use.
>
> For working on the CPU I hope to be able to use "git bundle" to distribute the state of work on vuln-dev (Similar to what we do with hg bundle now) and eventually push the release via a Merge PR. I will explore this in detail in the next weeks and see if it's bound to work. In case I don't see it working, I'd consider it a showstopper. So I'll update you on this soon, in time before the advised github switch.
> 
> > My own attempts to backport to jdk13u suggest the tooling still needs
> > work on this, or at least better documentation. [0]
> 
> I think you have a point here. As far as I know the "git backport" command does not exist yet and also the process to backport a change by commenting "/backport" on the original change in the jdk repository is not activated yet. I've brought this up to the skara team and they said that they hope to be able to enable it soon [1]. At the moment a backport would work like documented in the manual steps of this link [2] - which is not too convenient. I'll approach Skara folks again about that.
>

This all sounds like deploying this in just four months is too soon
for me. Why not allow Skara to mature first, if we must use it at all?

Can we not just switch 11u to git only and retain the existing processes that work fine?

> > OpenJDK 16, the first release to use git during development, has not
> > even been released yet. Why the rush?
> 
> Well, I would not consider it to be in a rush, given the proposal of switching in about 4 months from now. But overall, to align processes, to me it seems favorable to go to git with 11u and we should not overly delay it. At that time JDK16 and its first update release 16.0.1 will have been delivered out of git (as well as a few jdk13u update releases).
>

It's less git I'm concerned about, than that it seems to bring along
Skara with it. I found jcheck painful enough with Mercurial. Skara
terrifies me and seems to steal a lot of control away from us.

> > I don't see any reason at all to start altering 8u at such a late
> > stage in its development.  All risk and no gain.
> 
> That's a different discussion which I won't take part in as I'm not involved so much in 8u. The only point I have on that is that there's no reason to couple the decisions for 8 and 11, as was stated by Severin and Goetz already.
>

No, I agree on that. 8u is quite different and doesn't suffer from the painfully slow monorepo 11u does.

> Best regards
> Christoph
> 
> [0] https://github.com/openjdk/jdk/pull/2392
> [1] https://mail.openjdk.java.net/pipermail/skara-dev/2021-January/004051.html
> [2] https://wiki.openjdk.java.net/display/SKARA/Backports#Backports-CLI
> 

-- 
Andrew :)

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

PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222