ETA for next release

[o2sh]

Hi @XAMPPRocky,

Do you have an idea when the next release will be?

Since v12.1.2 was released in January 2021, there have been a couple of useful updates that onefetch is waiting for. Specifically #840 and #880 (not yet merged)

Cheers.

And thanks for the amazing work that you've done here 👍

[XAMPPRocky]

Thank you for your issue! There is currently no release date planned for the next release. I'm currently focused on other projects that have paid work attached to them. That's not to say there won't be a new release, I just have a few things I want to implement before releasing the next version. Right now it could be within the next three months, by the end of the year, or next year depending on when and how much time I get to work on tokei.

(P.S. If you'd like to see a release happen sooner, sponsorship support directly affects how much time I can spend on projects like tokei https://github.com/sponsors/XAMPPRocky)

[CosmicHorrorDev]

I should have some spare time coming up, so if you are kind enough to throw together a roadmap linking to issues you would like to be worked on then I should be able to pick up some work :D

[XAMPPRocky]

@LovecraftianHorror Thank you for the kind offer, however as you can probably tell, I don't have much time to respond to issues, so I wouldn't even have the time to create a whole plan and all the subsequent sub-issues, and while there are some features I want to add, not all of them are straightforward additions, some are infrastructure problems that require my credentials, some are much more bespoke problems that require a lot of design work that I need to work on to see if it's even possible, so I wouldn't want to create a plan saying "there will be a feature that does X, Y, Z" when I don't know if I can cleanly fit it into the current project or if it's really a good idea at all.

That being said of course, PRs for issues marked with help wanted are always welcome, and if there's something where I know what would need to be required, I'll try to make issues in case I don't have the time to immediately implement it.

[ErikSchierboom]

@XAMPPRocky I was wondering if you perhaps have an idea when the next release would be? #920 was merged relatively soon, and we'd like to use it in our systems.

[XAMPPRocky]

@ErikSchierboom No, the above message hasn’t changed. If you’d like to use latest you can always install from main with cargo.

cargo install --git https://github.com/XAMPPRocky/tokei.git

[ErikSchierboom]

@XAMPPRocky Okay, thanks for the quick reply!

[kornelski]

@XAMPPRocky Could you reconsider your plans? Outdated dependencies are a pressing problem. Bigger improvements can wait, but it'd be great to just have tiny maintenance release that fixes the deps.

[XAMPPRocky]

@kornelski I can't reconsider what I do not have the bandwidth to do. There are already breaking changes in main and I do not have the bandwidth to backport all the fixes. If they are so pressing then where is the money to fund this urgency? Currently GitHub sponsorships don't even cover a tenth of my rent, so please understand that your urgency to get timely fixes is trumped by my urgency to keep the lights on.

[spenserblack]

Would you be open to contributors backporting the fixes? If you make a branch like v12 from the latest release tag, I'm sure some users that are looking forward to a new release would be happy to backport those fixes (and non-breaking features) via PRs targeting that branch for you.

[XAMPPRocky]

@spenserblack If I don't have time to do it myself, I certainly don't have to review other people's work. I appreciate that people want to help, but just throwing more labour at the problem requires more time and work on my part to manage it all which is the exact thing I can't do right now. This a problem that's only solved by enabling me to spend more time on tokei, and until that's possible, people can expect to wait.