Release 1.17!?

[jpmh1309]

When will release 1.17 be created?

[henry2cox]

My personal bias is to get to the bottom of #185 (at least) first...but I guess there will always be a list of open issues and pending enhancements and we have to draw a line somewhere. (For #185, the current behaviour is no worse than in the past...though neither is it better).

With respect to numbering: there have been really a lot of changes to the lcov implementation - so probably reasonable to call it version "2.0".

Peter was hoping to let motivated users (self identified by downloading code from head/TOT) test the new functionality for a while, first.

Henry

[oberpar]

To add to what Henry said:

• Next version will be named 2.0
• We need to have a look at which open issues can be closed before that release
• Then I'd like to see a period of stabilization before the release, i.e. something like: no new feature commits for 2-3 weeks to allow our user base to report any remaining high-priority issues

A current rough estimate for release 2.0 would be somewhen in February/March 2023

[alkino]

Peter was hoping to let motivated users (self identified by downloading code from head/TOT) test the new functionality for a while, first.

I am trying the master on a middle-size project.

[mdskrzypczyk-aliro]

@oberpar @henry2cox thank you so much for all the work you do on this great tool. I am really looking forward to the filtering functionality added as it will greatly improve the accuracy of our code coverage reports. Is there any update on release 2.0 given it is now May 2023?

[henry2cox]

I may have been shooting Peter in the foot of late.
He wanted to have a couple of weeks of stabilization/no new commits...and I keep adding stuff.

[oberpar]

@henry2cox is definitely at fault here for adding so much cool new functionality 😄 (and maybe a hint of perfectionism on my side). I'm currently working on this with top priority but it will likely be at least another week before lcov release 2.0.

[mdskrzypczyk-aliro]

Much appreciated @henry2cox and @oberpar!

[henry2cox]

Peter just made the 2.0 release...so closing this issue at last :-)