Next release? #1079

brandon-arnold · 2017-05-04T13:43:58Z

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 · 2017-05-22T14:56:29Z

I want to know too.
Thanks

GJ

4brunu · 2017-05-22T15:28:47Z

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

SylvainCorlay · 2017-07-05T14:13:10Z

A 1.8.1 including the fix for mingw support (#721) which was merged right after the last release would be greatly appreciated.

petko · 2018-01-17T11:25:31Z

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 · 2018-03-27T17:54:33Z

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 · 2018-03-28T13:14:46Z

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 · 2018-03-28T13:19:50Z

See #1366

…

On Wed, Mar 28, 2018 at 9:14 AM Paul Smith ***@***.***> 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 <#1079 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMJSMmRaKN97FBSaTVvkMzBAdXLSFLPsks5ti4zSgaJpZM4NQsHz> .

madscientist · 2018-03-28T13:51:10Z

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 · 2018-03-28T14:01:31Z

@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 · 2018-03-28T15:16:31Z

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

henryiii · 2018-04-04T14:06:53Z

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

gennadiycivil · 2018-04-04T14:35:40Z

@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 · 2018-04-04T14:38:24Z

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 · 2018-04-04T14:50:39Z

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 ***@***.***> 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 <#1079 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMJSMvUvGRdL3C-Xi0vs7201PDExwe7kks5tlNrsgaJpZM4NQsHz> .

gennadiycivil · 2018-04-13T13:05:32Z

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

zz-pony · 2018-06-29T23:57:53Z

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

m-tmatma · 2018-06-30T00:05:54Z

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

SylvainCorlay · 2018-08-12T11:53:31Z

Is there any blocker for tagging 1.8.1 ?

gennadiycivil · 2018-08-13T14:14:41Z

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

gennadiycivil · 2018-08-31T17:07:26Z

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

bilelzouari · 2019-07-24T16:05:23Z

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

gennadiycivil · 2019-07-24T16:50:14Z

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 ***@***.***> 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 <#1079?email_source=notifications&email_token=ADBFEMX363BLH23BHVN64I3QBB4WFA5CNFSM4DKCYHZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2W2FLA#issuecomment-514695852>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADBFEMWOXPRY4DYLQIKFCQLQBB4WFANCNFSM4DKCYHZQ> .

This was referenced May 23, 2017

Release 1.8 Changes missing #855

Closed

googletest 1.8 release #586

Closed

bjornfor mentioned this issue Jan 3, 2018

When will there be a new release? #1342

Closed

alexkaratarakis mentioned this issue Jan 17, 2018

Fix error C4996 of GTest. microsoft/vcpkg#2592

Closed

ArekPiekarz mentioned this issue Feb 13, 2018

new gtest release - support options no_main and debug_postfix bincrafters/community#111

Closed

henryiii mentioned this issue Apr 4, 2018

Make a 1.9.0 release #1467

Closed

gennadiycivil mentioned this issue Apr 13, 2018

Skipping tests at runtime with GTEST_SKIP() #1544

Closed

piponazo mentioned this issue Apr 27, 2018

gtest packages without Combine feature bincrafters/community#240

Closed

gennadiycivil closed this as completed Aug 31, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Next release? #1079

Next release? #1079

brandon-arnold commented May 4, 2017

jhanggj commented May 22, 2017

4brunu commented May 22, 2017

SylvainCorlay commented Jul 5, 2017

petko commented Jan 17, 2018 •

edited

Loading

SylvainCorlay commented Mar 27, 2018 •

edited

Loading

madscientist commented Mar 28, 2018

gennadiycivil commented Mar 28, 2018 via email

madscientist commented Mar 28, 2018

gennadiycivil commented Mar 28, 2018

SylvainCorlay commented Mar 28, 2018

henryiii commented Apr 4, 2018

gennadiycivil commented Apr 4, 2018 •

edited

Loading

henryiii commented Apr 4, 2018 •

edited

Loading

gennadiycivil commented Apr 4, 2018 via email

gennadiycivil commented Apr 13, 2018

zz-pony commented Jun 29, 2018

m-tmatma commented Jun 30, 2018

SylvainCorlay commented Aug 12, 2018

gennadiycivil commented Aug 13, 2018

gennadiycivil commented Aug 31, 2018

bilelzouari commented Jul 24, 2019

gennadiycivil commented Jul 24, 2019 via email

Next release? #1079

Next release? #1079

Comments

brandon-arnold commented May 4, 2017

jhanggj commented May 22, 2017

4brunu commented May 22, 2017

SylvainCorlay commented Jul 5, 2017

petko commented Jan 17, 2018 • edited Loading

SylvainCorlay commented Mar 27, 2018 • edited Loading

madscientist commented Mar 28, 2018

gennadiycivil commented Mar 28, 2018 via email

madscientist commented Mar 28, 2018

gennadiycivil commented Mar 28, 2018

SylvainCorlay commented Mar 28, 2018

henryiii commented Apr 4, 2018

gennadiycivil commented Apr 4, 2018 • edited Loading

henryiii commented Apr 4, 2018 • edited Loading

gennadiycivil commented Apr 4, 2018 via email

gennadiycivil commented Apr 13, 2018

zz-pony commented Jun 29, 2018

m-tmatma commented Jun 30, 2018

SylvainCorlay commented Aug 12, 2018

gennadiycivil commented Aug 13, 2018

gennadiycivil commented Aug 31, 2018

bilelzouari commented Jul 24, 2019

gennadiycivil commented Jul 24, 2019 via email

petko commented Jan 17, 2018 •

edited

Loading

SylvainCorlay commented Mar 27, 2018 •

edited

Loading

gennadiycivil commented Apr 4, 2018 •

edited

Loading

henryiii commented Apr 4, 2018 •

edited

Loading