Googletest: Next release?

[brandon-arnold]

Hello,

It looks like master is the only branch that builds on all systems for me, and not the most recent 1.8 release around 7 months ago. Is there plan to tag a new release any time soon?

-Brandon

[jhanggj]

I want to know too.
Thanks

GJ

[4brunu]

I'm also interested in this.
Maybe @BillyDonahue can help.
Thanks

[SylvainCorlay]

A 1.8.1 including the fix for mingw support (https://github.com/google/googletest/pull/721) which was merged right after the last release would be greatly appreciated.

[petko]

Please do something about tagging the new releases.

Right now it's quite confusing for people who are not monitoring closely the development of GTest. I don't know which commits are stable enough for production use. I use 1.8, but it references some TR1 items in the Standard Library and I started getting deprecation warnings in the latest compiler versions..

[SylvainCorlay]

It would be great if core developers could communicate on whether there will be a release or if people should use the master branch in their workflow?

More and more projects out there are relying on forks or arbitrary commits posterior to 1.8, and there is a number of issues open on this repository asking about the next release.

cc @gennadiycivil

[madscientist]

If GTest decides to go to a "continuous release" model (or really, even if it doesn't) I really would love to see a NEWS file or similar updated in commits that add major new features, important bug fixes, etc. with a description. The Git history doesn't really help: it's a long list of "merge pull request" commit messages, mostly without information about what was actually changed.

I really have no idea what changes I'm getting if I take a cut of the Git repository.

Thanks!

[gennadiycivil]

See https://github.com/google/googletest/issues/1366

On Wed, Mar 28, 2018 at 9:14 AM Paul Smith [e-mail] wrote:

If GTest decides to go to a "continuous release" model (or really, even if
it doesn't) I really would love to see a NEWS file or similar updated in
commits that add major new features, important bug fixes, etc. with a
description. The Git history doesn't really help: it's a long list of
"merge pull request" commit messages, mostly without information about what
was actually changed.

I really have no idea what changes I'm getting if I take a cut of the Git
repository.

Thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/googletest/issues/1079#issuecomment-376882073,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMJSMmRaKN97FBSaTVvkMzBAdXLSFLPsks5ti4zSgaJpZM4NQsHz
.

[madscientist]

Thanks for the pointer! I'm afraid I'm a little too slow today to grok it fully. Are you saying that all the changes being made are related to C++11 support and no other changes to GTest are happening, so no NEWS-type file is necessary because there aren't any functional improvements (only rewrites to C++11)?

Or are you saying that the description of how GTest is going to be developed and released going forward is defined by the comment discussing Abseil compatibility policies in the second paragraph?

In either case I still think it would be a good practice to maintain a NEWS or CHANGES file. It may currently have only one entry ("Convert GTest to C++11"), but it will give a good place to add information in the future. If there are no more releases, there won't be release notes or whatever. It's good if the documentation is up to date and we can always get the latest code (due to compatibility guarantees), but scanning the documentation to see what improvements might have been made since the last time we used GTest, that we can take advantage of, is not really feasible.

There is already a CHANGES file available, but it doesn't seem to have been updated since 1.7.0.

Also it would probably be helpful to users to update the front-facing README.md file with information on the release model using Abseil now, instead of having it stashed in a Git issue.

Thanks!

[gennadiycivil]

@madscientist Just a clarification

• There is on-going merging work that will result in 1.8.1 being produced. The 1.8.1 will be the last release that works with pre-C++11 compilers. The 1.8.1 will not accept any requests for any new features and any bugfix requests will only be accepted if proven "critical"

• After 1.8.1 is ready , the work will start to remove C++98 support / cleanup code in the master branch At some point when this work is completed there will be a 1.9.0 tagged release and after that googletest will follow Abseil compatibility policies.

The question about NEWS file and CHANGES file is orthogonal to this process.

HTH
G

[SylvainCorlay]

Many thanks @gennadiycivil for the update, and more generally for all the work on maintaining and pushing googletest forward.

[henryiii]

That's great, @gennadiycivil! Will the current changes in master go into 1.8.1 or 1.9.0?

[gennadiycivil]

@henryiii , the plan is for the current changes in master to eventually culminate in 1.8.1 . After that master becomes subject to general cleanup and removal of old C++98 baggage which will result in 1.9.0.

[henryiii]

Thanks for the clarification, that would be great!

(PS: Not that it matters, but why not call that 1.9 and then make the C++11 only support version 2.0? I'm sure this discussion was held at some point.)

[gennadiycivil]

Good point. We can do bikeshedding
https://en.wiktionary.org/wiki/bikeshedding on the name to our hearts
pleasure when ready.

On Wed, Apr 4, 2018 at 10:38 AM Henry Schreiner [e-mail]
wrote:

Thanks for the clarification, that would be great!

(PS: Not that it matters, but why not call that 1.9 and then make the
C++11 only support version 2.0?)

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/google/googletest/issues/1079#issuecomment-378623077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMJSMvUvGRdL3C-Xi0vs7201PDExwe7kks5tlNrsgaJpZM4NQsHz
.

[gennadiycivil]

Another update, time-wise. No promises but we anticipate making 1.8.1 release in the coming months.
Hope this helps.

[zz-pony]

Thanks for working on a new release. I can't help asking, when will 1.8.1 become ready?

[m-tmatma]

Please don't release without fixing #1595(#1606).

[SylvainCorlay]

Is there any blocker for tagging 1.8.1 ?

[gennadiycivil]

Should be "really soon now", cant promise exact date.

[gennadiycivil]

https://github.com/google/googletest/releases/tag/release-1.8.1

[bilelzouari]

will there be a release for GTEST_SKIP() or not yet? thanks

[gennadiycivil]

Yes, - there will be a next release based on the current master.
https://github.com/google/googletest#future-plans

Thanks
G

On Wed, Jul 24, 2019 at 9:05 AM bilelzouari [e-mail]
wrote:

will there be a release for GTEST_SKIP() or not yet? thanks

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/googletest/issues/1079?email_source=notifications&email_token=ADBFEMX363BLH23BHVN64I3QBB4WFA5CNFSM4DKCYHZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2W2FLA#issuecomment-514695852,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADBFEMWOXPRY4DYLQIKFCQLQBB4WFANCNFSM4DKCYHZQ
.