googletest 1.8 release

[samkellett]

There hasn't been an official release of gtest since 2013. Since then support for movable objects has been added (ByMove, etc.) as well as other stuff I'm sure.

Is there any plan for an official release?

[BillyDonahue]

Soon!

On Wed, Sep 16, 2015 at 5:41 AM, Sam Kellett notifications@github.com
wrote:

There hasn't been an official release of gtest since 2013. Since then
support for movable objects has been added (ByMove, etc.) as well as other
stuff I'm sure.

Is there any plan for an official release?

—
Reply to this email directly or view it on GitHub
#586.

[samkellett]

How soon we talking?! 😄

[BillyDonahue]

It's a Q4 goal, so before 2016.

On Wed, Sep 16, 2015 at 3:46 PM, Sam Kellett notifications@github.com
wrote:

How soon we talking?! [image: 😄]

—
Reply to this email directly or view it on GitHub
#586 (comment).

[samkellett]

That's awesome! Cheers for all the hard work

[jupp0r]

Cool, do you have any update on the roadmap? I understand 1.8 will support C++11/14 ?

[BillyDonahue]

v1.8 will not be C++11/14 capable.
It will just be a snapshot of what's basically trunk right now.

When we have v1.8.0, we will have something relatively modern that people
can use even if they are stuck without a C++11 compiler. So they'll be
happy for a while while we go off into the future.

After v1.8.0 is tagged and released, we'll start breaking some
backward-compatibility with pre-11 compilers in head.
This applies to user support as well as the internals. If you look at the
implementation internals for googletest and googlemock, you'll see a lot of
places where C++11 would have saved us a lot of complexity and workarounds.

On Wed, Nov 25, 2015 at 6:56 PM, Jupp Müller notifications@github.com
wrote:

Cool, do you have any update on the roadmap? I understand 1.8 will support
C++11/14 ?

—
Reply to this email directly or view it on GitHub
#586 (comment).

[jupp0r]

Thanks for the clarification.

[xor-gate]

2015-Q4 has passed :_)

[BillyDonahue]

Working on it!

On Wednesday, January 6, 2016, Jerry Jacobs notifications@github.com
wrote:

2015-Q4 has passed :_)

—
Reply to this email directly or view it on GitHub
#586 (comment).

[anatol]

Any update? I would like to bring this package to Arch Linux but the last release is too old. Any chance to see a new release (well at least -rc release) in the nearest future?

[dcow]

What's blocking this?

[BillyDonahue]

There's no blocker, just need the time to work on it.

On Thu, Mar 24, 2016 at 6:24 PM, David notifications@github.com wrote:

What's blocking this?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#586 (comment)

[eelstork]

The lack of a recent release does have minor downsides.

[lteich]

The googlemock cockbook says that googlemock supports move-constructible return types, but this (as far as I can see) is not supported in the latest official release. Maybe the cookbook should be made clearer, denoting the experimental\non-release features, and giving workarounds for current official releases.

[Gordon-Mc]

Looks like gtest v 1.8.0 does now exist - but I see no information on what is new in this release. Unless I'm hallucinating (always possible :-)) the CHANGES file in the 1.8.0 download lists what is new in 1.7.0, not what is new in 1.8.0.
Can anyone point me to details of the 1.7.0 -> 1.8.0 changes ?
Thanks.

[KindDragon]

Related to #855

[KindDragon]

Can anyone point me to details of the 1.7.0 -> 1.8.0 changes ?

release-1.7.0...release-1.8.0
548 commits

[matthauck]

548 commits is a bit much to consume... 😢 Perhaps you could produce some bullet point release notes to help point out what is new / improved / changed in 1.8?

[abozkurt]

When are you planning to update 1.8 changelog? Thanks.

[Croydon]

Is there seriously still no changelog for 1.8?

[KindDragon]

Related to #1079