A new release?

[zhihaoy]

I hope we can release more regularly so that we can update vcpkg accordingly.

[ColinH]

Just to be clear, do you mean that we should release more frequently and/or on a predetermined fixed schedule?

[zhihaoy]

More frequent than once every 3 months would be good. Source-based ports systems (including FreeBSD ports) can easily catch up indeterminate very frequent releases, but if too long time without seeing a new release things (build scripts, patches, etc. in the port) can get decay.

[d-frey]

We usually release quite often as long as there is something new to release. The exception is major versions, as we do not want to break the API every couple of month.

That is the reason why the next release (3.0.0, switching to C++17) is in limbo for some time now, we need to come up with a plan which changes should still go in before a new major version. Colin and me will talk about it at the weekend, hopefully we can release 3.0.0 soon.

[zhihaoy]

I didn't released that 2.7 isn't C++17-only. Okay, I filed an issue to ask around microsoft/vcpkg#5337.

[d-frey]

We've backported all features from the C++17 HEAD version back to the 2.x branch (unless they rely on C++17). Check the Changelog for the details. A new release of the 2.x branch will be done in the near future, we don't expect any major new features, just final details and documentation.

[d-frey]

We released version 2.8.0, which is still compatible with C++11. There is currently no estimate for a 3.0.0, the 2.x branch will be maintained as necessary.

[zhihaoy]

Thanks for the update. I'm not using using 2.x but I can update vcpkg accordingly...

[d-frey]

OK, thanks!