Delay between GitHub release and Blog Post

[danilofuchs]

Hi all, thanks for the awesome work!

I'm a subscriber of Deno Releases on GitHub. Every time a new version is published, I get notified by email. Then I go to check the changelog but it is too low-level, so I prefer reading the blog post at deno.com/blog

I'm noticing this post is consistently delayed by a few hours or days.

By having this delay, we are loosing the very small window of opportunity between users receiving a notification and engaging it. If it is too difficult to read the release notes right after being notified, people will end up disabling them, reducing further engagement.

I suggest one of the requirements for major/minor releases is to have the blog post ready and link to it when releasing on GitHub. As a developer, this wouldn't be something I like waiting for when releasing, but as a business standpoint it seems to make sense to me.

[danilofuchs]

What I end up doing is refreshing the blog every hour just to see if the release notes are up.
I'm not interested in other content in the blog, so I don't sign up for the RSS feed.