Plans for upcoming version

[alipov]

Hi there! :)
Hopefully this is a suitable place to ask.
I'd be grateful if you could share plans for upcoming version release (it's been over a year since the last one). For what it's worth, I'm specifically waiting for #1945 and #2401 to be part of an official build.
Thanks!

[eamonnmcmanus]

Hi, we have indeed discussed making a new release. I think @Marcono1234 had a short list of things that should ideally be included, and perhaps can comment on whether any of them are still missing.

[Marcono1234]

#2588 would probably be good to include (see private discussion we had).
#2556 might be nice to have, but might have to be adjusted depending on whether you think this approach is ok.

---

#2619 is only about documentation and can be delayed (or rejected).

#2571 and #2573 probably need some testing / investigation regarding which approach (if any) we want to use to address this. So maybe we should wait with them until after the release.

[Marcono1234]

@eamonnmcmanus, could you please also have a look at #2648 before the release?
I just noticed that we can support strict parsing there as well in a backward compatible way.

[eamonnmcmanus]

@eamonnmcmanus, could you please also have a look at #2648 before the release?

OK. I think we can add #2648 and #2588 and then make a release. We can always have another release after a short while with some of that other stuff. For #2588, I just need to fix one of Google's internal tests that will fail with that change.

[Reginer]

I'm specifically waiting for #2401 to be part of an official build.
Thanks!