Den tors 11 feb. 2021 kl 10:31 skrev Daniel Sahlberg < daniel.l.sahlb...@gmail.com>:
> Den tors 11 feb. 2021 kl 10:11 skrev Stefan Sperling <s...@apache.org>: > >> 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? >> > > Sure, I'll make a suggestion in staging. Not today though. > I've committed an initial suggestion in r1886494 ( http://subversion-staging.apache.org/docs/community-guide/releasing.html#releasing-release ). Kind regards, Daniel Sahlberg >
