"long-term" C++14 support branch based on 3.6.0?

[insi-eb]

we are using CppMicroServices in an environment where at least in the next year or so, we cannot move to C++17.

Is there any interest for including a C++14 support branch based on 3.6.0 in this repo, if we would step in and do the work to backport important bugfixes (where possible) and update 3rd-party dependencies to such a branch? Or should we just fork the repo and do what we need on our fork?

[jeffdiclemente]

@insi-eb , absolutely we are ok with a C++14 support branch. If you are willing to backport the fixes you need in a fork, we can create a branch in this repo for you to merge into from your fork. There are probably others who would benefit from a C++14 support branch so having it generally available on a dedicated branch in this repo would be beneficial.

Let me know if this is acceptable to you.

[insi-eb]

I'm fine with staying on a 3.6.x versioning scheme even though features are added to stay merge-compatible with 3.7.2. Internally we also now use the C++14-branch as a 3.6.1
If this is too confusing to users, there still is the explicit versioning scheme as fallback.

I'll create a PR for that as soon as I find some time again - should not take too long.

Btw, is there a reason 3.7.4 has not been merged to master?

[jeffdiclemente]

Btw, is there a reason 3.7.4 has not been merged to master?

no reason other than we haven't gotten to it yet.

[insi-eb]

@jeffdiclemente: shall I do anything more for a 3.6.1 release from the C++14 branch or will you handle that (e.g. merging c++14-compliant to the release-3.6 branch and creating a tag)?

[jeffdiclemente]

@insi-eb I'll merge c++14-compliant into the release-3.6 branch and create a tag (3.6.1) today.

[jeffdiclemente]

@insi-eb All set. I created a new release as well under https://github.com/CppMicroServices/CppMicroServices/releases. Let me know if anything looks wrong and I'll fix it.