Next release?

[suhrig]

Dear Fabio,

I ran into a bug in riboWaltz, which to my positive surprise I found to have been fixed already in bc6b733. That's great!

However, I'm using riboWaltz in a nf-core pipeline, which pulls riboWaltz through bioconda (as usual). So in order for me/the wider community to benefit from this bugfix, you would need to tag a new release on GitHub, such that bioconda triggers a build of the new version including the bugfix. The current 2.0.0 release is more than two years old. What's your timeline on publishing the next release?

Best regards,
Sebastian

[fabiolauria]

Hi Sebasrtian,
I apologize for the late reply.

Thank you for using riboWaltz. I'm aware that the latest release is superold, and I'm sorry for that. Unfortunately, throughout the year I can usually dedicate only 10–20 minutes here and there to maintaining the package. The only period when I can really focus on updates, testing, and preparing a new release is during the Christmas holidays.

Keeping riboWaltz up to date is always one of my priorities. However, before publishing a new release I need enough uninterrupted time to carefully review all the changes made since the previous version, verify that everything works as expected, and go through the open issues and their related fixes. I prefer taking a bit longer rather than releasing a version that hasn't been thoroughly checked.

A new release is definitely on my to-do list, but at the moment I can't provide a reliable timeline. Thank you for your patience and understanding.

Best
Fabio