-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag 0.22? #22
Comments
Just wanted to comment quickly - the request's not forgotten, I'm just really busy the ol' day job, and tagging a new release is only something I'll do after more thoroughly double-checking the state of master. Apologies. |
@seanmiddleditch fluffos has been using latest commit for a while now, and it seems pretty OK. |
Now that is the bug we fixed. It's time to put a new release out to notify people to upgrade to this. |
It's on my radar, but I'm pretty busy. Feel free to ping me on this if I don't get to it soon (or send me pull requests to get all the release stuff handled, and then I can tag the release commit). |
like to know too about a new release tag ^_^ |
I'd like to get onto CMake before doing a 0.22, but it's been a few years and we have some good fixes in the pipe. I'm actually working on something telnet-related for the first time in years so I'll try to remember to roll a release for libtelnet soon - please feel free to keep bugging me (or put up a PR prepping the release, e.g. rolling version to 0.22 in develop and the merge request into master) if I continue to slack. :) |
I gave up on getting to CMake in a timely manner so it's tagged and released. :) |
Ahoy, it's been quite some time since
0.21
's release. Would you consider pushing a new tag? This is particularly helpful for me, as I pull libtelnet into my project using CocoaPods and I'd much rather point to a tag (rather than a commit). Thanks!The text was updated successfully, but these errors were encountered: