Freeze/Unfreeze tree and land clang-format changes Dec 9.

[bob-beck]

We will need the tree frozen at various points to land the clang-format changes without significant pain.

Assuming the preparatory stuff is ready, I would like to start landing this for head of tree at 0000 hrs my time on Dec 9, which is 0200 US eastern time, 0700 UTC time (0800 Czechia time)

For reference, see Here

Staring with the head of tree, this looks like:

• Ensure Neil has permission to merge changes to the frozen tree (dima)
• Freeze the tree at 0700 UTC / 0800 CZ time (dima)
• Generate and land last minute preparatory changes if any.
• Tag the tree with 4.0-PRE-CLANG-FORMAT-WEBKIT (committer?)
• Land the clang-format changes on head of tree. (bob / committers)
• Wait for CI to pass.
• Get the commit hash for the the above, and and add it to .git-blame-ignore-revs, landing that. (committer? bob)
• Tag the tree with 4.0-POST-CLANG-FORMAT-WEBKIT (commiter?)
• Enable clang-format enforcement on CI / Disable legacy code style check. (dima)
• Unfreeze the tree once all of that lands. (dima)

This would get us to the point where development can continue on HEAD.

At this point we would like to repeat this process for(in order)

3.6
3.5
3.4
3.3
3.0

We will not do 3.1 and 3.2 in the public repository, as they are supposedly "dead" - we could do them in the private repository.

This will require assistance from someone to do the tree freeze/unfreeze, and committers to approve the changes landing and do the tree tagging

[bob-beck]

I have tenatively tagged nhorman and sashan in on this to perhaps coerce them into being the committers to help me out with this on the day of.

It need not be you, but I will need someone with committer access and who is familiar with our stuff.

[t8m]

3.1 and 3.2 SHOULD NOT get any changes in the public openssl/openssl repo! You can do whatever with them you wish but only in the private openssl/premium repo.

[t8m]

The format changes will need formal approval by two committers (i.e., Reviewed-by annotations) - maybe it is obvious but I just mentioned that to make it clear.

[nhorman]

I'm fine to be the freeze person, if you like @bob-beck

[bob-beck]

3.1 and 3.2 SHOULD NOT get any changes in the public openssl/openssl repo! You can do whatever with them you wish but only in the private openssl/premium repo.

Ahh this was something I was not aware of, as I've never touched those, I'll have to get someone to help me out with that.