New release process?

[ckentgeorge]

What needs to be done to get a new release to haxelib?

[misprintt]

Hi @ckentgeorge,

As far as i'm aware, none of the original contributors are active in the Haxe community, and this project has been mostly dormant for many years.

Due to the nature of how code coverage works. mcover requires significant effort to update/support each new versions of Haxe (as it is tightly coupled to changes in the macro APIs)

I'd suggest looking into the more active forks and maybe reaching out to @AlexHaxe?

[ckentgeorge]

Interestingly, the latest code works, although I suspect isn't backwards compatible. this latest changed with 4.3.x was a pretty minor breaking change. I think mcover still has legs. Does this project need a new maintainer? It'd be great to publish to haxelib, but I'v never looked into that.

[AlexHaxe]

not sure I can really help much. I mean I'm still using mcover for checkstyle and formatter tests (mostly because I haven't moved them to utest), so I'm keeping my branch working with current Haxe versions as much as possible, but I'm not implementing any new features and I'm not really trying to push for new releases (they do happen occasionally, or at least they did in the past, but it might take weeks or months).

I do have my own coverage library called instrument, but even that currently has no solution for NullCoal and safe navigation operators (waiting on a fix on Haxe's side).