Possible announcement needed for drop of s390x in bookworm

[MikeMcC399]

I think this is ok although we should consider whether we need to make a wider announcement on this somewhere (e.g. in the upcoming releases - FYI @richardlau)

If we do I think it should be its own announcement as it doesn't just affect one release line.

There doesn't appear to be a precedent for announcing changes to Node.js Docker images. Perhaps the release team would like to decide if the regular Node.js blog should be used for this. If so, it should probably be added as guidance to the CONTRIBUTING document, so that significant updates get their own blog announcement prepared.

This should probably be a separate topic here anyway.

Originally posted by @MikeMcC399 in #2557 (comment)

[richardlau]

I think this is ok although we should consider whether we need to make a wider announcement on this somewhere (e.g. in the upcoming releases - FYI @richardlau)

If we do I think it should be its own announcement as it doesn't just affect one release line.

There doesn't appear to be a precedent for announcing changes to Node.js Docker images. Perhaps the release team would like to decide if the regular Node.js blog should be used for this. If so, it should probably be added as guidance to the CONTRIBUTING document, so that significant updates get their own blog announcement prepared.

It's not under the responsibilities of the @nodejs/release though (it was a responsibility under the Docker WG). Although as announcement channels, the Node.js blog on the website would be the default choice.