[crac] RFR: Merge jdk-17+35

[akozlov at azul.com]

On Mon, 27 Sep 2021 14:44:54 GMT, Dan Heidinga <github.com+8503711+DanHeidinga at localhost> wrote:

> What's the preferred process on this kind of change? I'm new to managing merges of the JDK mainline into project specific repos so not yet clear on what level of review something like this would need.

I'm not sure also :) But I wanted to provide a heads up at least for the bump of the major version. Merges of minor versions probably are OK without review, if we'll do them often.

> > All CRaC-specific tests pass, although there are only few of them.
> 
> As this is a merge of mainline (well, 17) I'm OK with giving this the +1 assuming that's the process we typically follow for this?

Yeah, I think this would be useful, a simple acknowledgment from other member(s). 

> Do projects typically follow the releases or the mainline development? Still learning the norms here :)

We are free to choose something most suitable for us. I think having both makes sense: following mainline development for fast resolution of the problems with merges and a stable release for users to try. However, it is an additional burden in maintenance. Having 17, the merge of the early pre-18 state should be simple, the opposite looks harder. So for following 17 looks useful but simple enough. We can extend this any time we'd want, I think.

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

PR: https://git.openjdk.java.net/crac/pull/2