Googletest: When it will be new gtest release?
We want to use new feature to check the exception message #2904. It was merged to master on Aug 23, 2020. But currently this code is not included into any existing releases / tags.
Last release was more than a year ago. Oct 3, 2019
// EXPECT_THAT(
// []() { throw std::runtime_error("message"); },
// ThrowsMessage<std::runtime_error>(HasSubstr("message")));
apivovarov
All 3 comments
Quote from the README:
Post 1.10.x googletest will follow Abseil Live at Head philosophy
You should pull directly from master and not from a version tag.
friendlyanon
on 20 Nov 2020
From: https://abseil.io/about/philosophy#if-you-choose-to-not-live-at-head
We will periodically mark a tag as “supported” and branch it — if we discover security issues or major performance problems, we’ll update those branches. Our expectation is to do this every 6 months and support those branches for 2 years.
So my expectation is that at least some known good tags are published, and the laste one was the 1.10 release. Or if you plan to not follow the abseil policy in that regard please state so.
Ozaq
on 26 Nov 2020
Although we in general follow Abseil's Live-at-Head philosophy, we haven't looked into doing an LTS release yet. Thank you for raising this, we need to clarify the policy. As far as a known-good tag goes, we don't really have such a concept - we simply try to keep all commits in a working state.
derekmauro
on 30 Nov 2020
Related issues
cyberdecker
·
3Comments
marknelson
·
4Comments
nholthaus
·
6Comments
markfrazzetto
·
3Comments
bofinbabu
·
6Comments
Most helpful comment
Although we in general follow Abseil's Live-at-Head philosophy, we haven't looked into doing an LTS release yet. Thank you for raising this, we need to clarify the policy. As far as a known-good tag goes, we don't really have such a concept - we simply try to keep all commits in a working state.