No Tag nor Release for v3.14.0

[claudiushaag]

Hey!

@louisepb thank you for your work!
It would be really great if there would be a tag and a release for the current software version, as this makes it clearer to point to the current software status.

Thank you!

[louisepb]

Hi Claud,
Version 3.14 hasn't been released at the moment. I'm afraid that if you want to access any of the additions to the code from after version 3.13 you will need to build the source code. I left Nottingham in July and am now at Birmingham university. Unfortunately I didn't have time to get a release done before then. We are waiting to hear about an application for funding for people (including myself) to maintain the software. Hopefully that will be good news and then we will be able to actively maintain again.
Best wishes,
Louise

[claudiushaag]

Hi Louise,

thank you for your response and the project in general! Its capabilities are very impressive. I falsely expected version strings in the codebase to be incremented right before a published github-release, not during the development, hence the question.

I'm working on a build-port of TexGen (or at least the Python-API) to conda-forge, in this PR.

This would make it quite easy to install TexGen with its binaries on all major OS, without needing to compile locally.
This would be as easy as doing

conda install texgen

and then having all the functionality in a conda-environment. I would expect that to lower the entry-barrier of using TexGen quite a lot, at least it would for us.

To package the current state, which differs quite from v3.13.1, my venture does not depend on a further development, but rather on a reliable code-reference, as in a tag to make sure the version is in accordance to the project and from a secure source, see here for more information.
If you would consider doing such a release / creating a tag, it would help this effort a lot and spare our time of getting v3.13.1 to compile instead of the already achieved v3.14.0.
Alternatively, it could already help to create a release for v3.13.2, which has no github-release and tag yet, as the current one here is v3.13.1, as can be seen here

[claudiushaag]

@louisepb this is a respectful reminder of this problem.

I understand the uncertainty in the scientific work environment, and if the maintenance of TexGen comes to a halt on your side, this is totally understandable.

If this is the case, a final release of the current state of software as v3.14.0 would be great, so there is one point of reference. Furthermore, some projects also transfer the repository to an organization and give a few people of the community maintainer-status, to enable further maintaining or bug-fixing, ensuring the scientific community can benefit of the great work TexGen is for a long time.