-
Notifications
You must be signed in to change notification settings - Fork 81
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
Release into Kinetic #5
Comments
ping - has support ended for this package? |
Hi, On Thu, Oct 20, 2016 at 9:01 PM, Dave Coleman [email protected]
|
You would have to give access to https://github.com/lrse-ros-release/keyboard-release.git to someone |
Friendly ping :) |
Any update in the kinetic release? |
Also interested! 😃 |
Hi,
I'm returning from holidays next week, so it is currently not possible for
me to deal with this. However, it would be nice if someone would be willing
to release it for kinetic since this package is not a priority for me.
Moreover, I will not add new features for the time being, but will only add
patches required for building correctly.
Assuming it is just a matter of giving access to the release repo, who
wants to do this? Let me know and I will give access.
El 20 ene. 2018 03:45, "Nick Walker" <[email protected]> escribió:
… Also interested! 😃
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJ3qtpzvDOosdedXofe40rgJmN0RhxGks5tMP7SgaJpZM4JBDhH>
.
|
Is there any update on this? |
Friendly ping again :) |
Hi @adam-pensa , as I mentioned in my last comment, I'm no longer maintaining this and anyone else is welcome to take care of keeping it released. I could transfer the release repo to someone if that solves the problem or maybe it would be easier to simple fork this repo and have someone else maintain it. |
Could we get this package released in kinetic? I have a downstream package that I cannot release yet because of it.
Thanks!
The text was updated successfully, but these errors were encountered: