On Thu, Feb 11, 2021 at 09:57:23AM +0100, Daniel Sahlberg wrote: > It is indeed a chicken-and-egg problem. However I would suggest to split > this "updating the website" into two separate parts: > 1. Updating the download page and possibly also adding a news item (with a > placeholder link to the release announcement) before the announcement. > 2. After the release announcement has landed in lists.a.o, update the news > item with a proper link. > > If the website is updated in one batch after the announcement someone might > receive the announcement, immediately heading to the download page and then > not finding the announced release.
Yes, that makes sense. Would you have time to update the web site accordingly? Having just run through the steps, I must say that our release manager's guide has a rather low signal-to-noise ratio in its current form. It may help to break some text into more paragraphs with meaningful headers, and/or perhaps put boxes around some of the details that don't really matter when someone is trying to get an overview of the procedure. Regards, Stefan
