Move 2.6.347 to release and add new release

[brendandahl]

It's been awhile. @timvandermeij do you have time to do a new one?

[Snuffleupagus]

Can we try and get PR #12726 landed first, such that it's included in the next release?

[timvandermeij]

Yes, we can do this, but it would be great to have that PR included if possible. Brendan, do you have time to finish that one?

[Snuffleupagus]

Unless PR #12726 is likely to be updated soon, should we perhaps do the following:

1. Create a new release ASAP, given how long it's been since the last one.
2. Once PR [api-minor] Include and use the 14 standard font files. #12726 lands, create a new release very soon afterwards. Given the potential impact of that PR, it might even warrant its "own" release anyway!?

[timvandermeij]

I'd be fine with that. @brendandahl Do you think that PR can be updated soon, or should we proceed with this release?

[brendandahl]

I've been looking into it. I'm trying to do some benchmarks, but unfortunately our current setup doesn't really measure the font conversion. I'm going to do some pushes to mozilla's talos to see how perf is there.

[Snuffleupagus]

Given that PR #12726 looks to be further from landing than I hoped, given the performance regressions, let's just create a new release ASAP :-)

The release notes, for the new release, should probably mention that IE 11 is now unsupported.

[timvandermeij]

Yes, I'll get this done today.

[timvandermeij]

The release is done. On NPM the next tag is already updated with version 2.7.570. @brendandahl Because of #12324 the latest tag is not updated again. Could you update it manually to version 2.6.347?

[brendandahl]

done

[timvandermeij]

Thanks!