Discussion: Should release announcements be skipped if delayed too long?

[adamfarley]

Not ideal to delay publishing a release blog post (which ideally gets published at the 7 or 8 day mark (after most platforms are published). When it is delayed, then the announcements from Eclipse Foundation go out very late...

Feb 12th this was published... which make it appear as though it took us a lot longer to release things than it really did (harms the project's public reputation). Wondering if we should give instructions to EF to not bother announcing if a certain period of time has passed.

Originally posted by @smlambert in #64

[adamfarley]

I suggest that we announce the release as soon as the builds are released on the primary platforms. This should not include a release note link.

For the release notes, this should be announced separately so it can't block anything.

[smlambert]

Release notes job can be run as soon as the build pipeline kicks off, and plunked into a blog draft that can be ready to publish at the point the primaries have all been shipped. Release notes generation doesn't block anything.

Related: adoptium/adoptium.net#2851

[smlambert]

Added reference to this in marketing call agenda to flag up to EF marketing team, so will close this now.