1.19 blog post

[duailibe]

ETA: 9/25

[lydell]

Looks like we forgot to add a changelog entry in #6157 – we need to add that to the blog post.

[duailibe]

I'll add, thanks @lydell

[fisker]

Should we mention parser-postcss.js is now minified? #6395

[kachkaev]

Would it be possible to wait for #6519 or can it be later released as 1.19.x?

[nikulis]

A few small spelling, grammar things :)

[duailibe]

I think any other updates should come in 1.20

[alexander-akait]

@duailibe i disagree, all issues/PRs marked as 1.19 should be competed (some PRs are very important, for example #6033 and #6400). We can discuss what PRs can be removed from 1.19 milestone, but we can't ignore them or just saying other updates should come in 1.20.

[duailibe]

@evilebottnawi Yes, what I meant was I don't think all the issues and PRs in the milestone need to be there and the release should not depend on that

[alexander-akait]

@duailibe i think we should resolve this issue for 1.19, some of them is very important. We don’t do releases very often so developers will have to wait a long time and we won’t get feedback on some issues/PRs

[lipis]

All set.. we just need to update the blogpost, and there are not leftovers in the 1.19 milestone.

[lydell]

I could finish this up this weekend, and probably do the release, too. Is it good to release on a weekend?

@duailibe Are you going to finish this, or should I take over?

@evilebottnawi @thorn0 @sosukesuzuki @fisker @brodybits Any comments?

[thorn0]

@lydell Don't forget that CHANGELOG.unreleased.md has been a little refined since this PR was created.

[lydell]

Yeah, I was thinking of starting from scratch from it.

[lydell]

Closing in favor of #6787.