Any plans to make first release?

[kloczek]

IMO it would be goog to make first release and tag git repo :)

[ebassi]

No real plan, at the moment. The main use case is embedding a sub-project.

I can spin up a release, but it's low on my to do list.

[kloczek]

Why not?
It looks like it can be used as DSO ..

[ebassi]

Why not?

Because that would require freezing the API, and would also require me to devote more time than I currently can spare.

I'm not closing the door on a release, but as I said, right now it's low on my to do list.

[kloczek]

So in current situyation it could be no repeatable builds of other projects ..

[ebassi]

So in current situyation it could be no repeatable builds of other projects ..

I have no idea what you mean with that. Linking against mutest as a shared library, or linking against mutest as a static library yield precisely the same result.

You can download a Meson subproject before running the build, and then build without a network connection, but that has nothing to do with reproducibility.

If you mean "pulling mutest from master means pulling different commits" then I'm sorry, but it's just a fact of life.

You could simply package mutest from the current tip of the main development branch, and only update if needed.

What you do not, in any way shape or form, get to do is come here and tell me to spend my time on what you want.

[kloczek]

Issue is that few packages uses mutest as part of the build env and to package mutest it would be good to have some version of mutest.
In case any futore changes in mutest API always major release can be published and tagged.

Really please tag what is even now as for example 1.0.0.

[kloczek]

In main meson build as version is used 2019.1 as version. What about bump it adnd tag whole tree as `2021.4'?