Blog post for 2.0

[thorn0]

https://deploy-preview-7417--prettier.netlify.com/blog/2020/03/21/2.0.0.html

[kachkaev]

What's the best way to mention changes in defaults (#6888 (comment))? These are still to be done, but I guess the PRs can land in the last minute.

[thorn0]

@kachkaev There will be a 'Breaking Changes' section in the blog post. But for the PRs to land, someone has to create them. Would you like to help with this?

[kachkaev]

I can give #6929 and #6932 a shot over this weekend. Is this OK with you time-wise?

Guess there is a consensus to not include #6931 into 2.0. I'm happy with that issue being closed. Would you add two others to the milestone if you have access, just so that we don't forget?

[thorn0]

I can give #6929 and #6932 a shot over this weekend. Is this OK with you time-wise?

I'll be away this weekend, so yes, sounds good. Please put the changelog entries into changelog_unreleased/api.

[kachkaev]

Please put the changelog entries into changelog_unreleased/api.

@thorn0 Done. Please see diffs in #7430, #7435 and #7441 🙌

[fisker]

Can we share this with lint-changelog.js? And I forgot add shebang on lint-changelog.js

[thorn0]

Yes, eventually it'll be shared, but so far I'm not sure where this script is going to end up. It might become part of the release script or else a page titled "Unreleased changes" might be generated every time the website is built. Or both these options.

[thorn0]

Docusaurus's syntax highlighting seems to not understand JS generators: one, two.

[fisker]

highlight.js version?

It's supported, just need another style with different color.

[thorn0]

@fisker I bumped highlight.js to the latest version, but it didn't help. Look how it is tokenized:

Doesn't look like switching to another theme might help here.

[fisker]

but helps the function* foo one

[thorn0]

This one isn't highlighted at all.

[kachkaev]

👋 @thorn0, what tasks are left to do before the team can release 2.0? How can I help?

[thorn0]

@kachkaev As I see it, two tasks are left: #7516, which is a simple revert, and #6776 + #7587, which is a bit trickier than it seems. If you could help with reviewing #7587, would be good.

[fisker]

@thorn0 Are we going to do this #4097 in 2.0?

[kachkaev]

@thorn0 many thanks for releasing 2.0, you are a star! 🌟 🙌

One minor thought about the blog post. Shall we replace Prettier stable and Prettier master throughout the examples into something a bit less confusing? Perhaps, Prettier 1.19 and Prettier 2.0 will serve well here. Happy to elaborate more on what I mean.

I can submit a PR with the above corrections if it's a go.

[thorn0]

@kachkaev Yes, please. I actually wanted to do this but forgot.

[lydell]

@kachkaev I used this format for the 1.19 blog post:

// Input
eventStore.update(id, _.flow(updater, incrementVersion));

// Prettier 1.18
eventStore.update(
  id,
  _.flow(
    updater,
    incrementVersion
  )
);

// Prettier 1.19
eventStore.update(id, _.flow(updater, incrementVersion));

[kachkaev]

@thorn0 and @lydell, thanks for your quick replies! See #7819. Hope I haven’t missed or broken anything 🤞

How about adding this versioning step to the Prettier release playbook? Guess it could be done in a separate PR. I don’t know much about your process, so happy to leave this with one of the maintainers 😉

[thorn0]

@kachkaev I added this step to https://github.com/prettier/prettier/wiki/Release-Checklist ✔

[kachkaev]

@thorn0 cool!

How about

replace "Prettier stable" and "Prettier master" in code examples with the actual versions

↓

replace "Prettier stable" and "Prettier master" in code examples with the actual versions ([example](https://github.com/prettier/prettier/commit/171bc96b58c0ebad702270389674eadfffec09d1))

The example commit can save from extra questions like Should I write "Prettier 2.x" or "Output (Prettier 2.x)". @lydell’s advice has helped me a lot with this.

[thorn0]

@kachkaev ✔ Thanks.