Cut a 2.2.1 release?

[qmfrederik]

There was a suggestion of cutting a 2.2.1 release here: #274 (comment)

On top of that, a lot of fixes MSYS2-related fixes were merged after the 2.2 release, together with PowerPC-related work: #272

@davidchisnall Given all that, do you think it makes sense to cut a 2.2.1 release?

[davidchisnall]

Yup, I think so. Is there anything in trunk that shouldn't be in the 2.2.1 release? Normally, I'd branch 2.2 to create 2.2.1 and then tag that.

[hmelder]

Is it possible to create a new ANNOUNCE file in this release?

[davidchisnall]

Yes. I think the best thing is to create a 2.2.1 branch from 2.2, cherry pick all of the fixes in, and create a new ANNOUNCE there.

[qmfrederik]

I can't think of anything which is in trunk which shouldn't be in 2.2.1, so I believe you could just branch master.

[davidchisnall]

The main thing is that the announce for trunk is now for 2.3.