On 11/21/18 10:53 AM, Ronnie Brunner wrote:
Hi Massimo
Both test suites run flawlessly on my system.
My only concern would be whether we should introduce a potential
incompatibility in a patch version or whether this justifies a minor
version upgrade... I'm torn, it seems a border case and I can live
with both as long as it was a conscious decision on your side and not
just by accident.
Gruess Ronnie
Ronnie
you are the person who got bothered checking the new artifacts and
commented, quite appropriately. I'd like to address your remarks and the
issue in the safest way and following the concerns you pointed out.
Creating a new branch and tag on git is a cheap operation. I will
create a patch of the last 2 commits, withdraw 3.0.4, reset the 3.0
branch back by 2 commits (the status it had before this potential
regression was introduced) and reapply the patch to a new 3.1 branch to
be released
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org