-
Notifications
You must be signed in to change notification settings - Fork 33
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 "releases" occasionally? #23
Comments
Adding you as a collaborator. Feel free to tag releases however works for you if you're up for that. Thanks! |
I didn't expect that, but thanks! If you are ok with it, I'll tag 0.1 once the nixos package lands. Do you use irc or matrix where I could shoot a message before cutting a tag? |
Yep, tag away. And, hm. I've switched jobs and mostly we just use Slack here. Also have a discord channel but don't look at that much. Maybe just tag as you see fit and I'll see it with github notifications. If you make any major changes to the code I'd like to take a look, but otherwise please do whatever you need to get your work done and make this useful. |
Thanks. I don't plan any changes except an occasional tag. This is an awesome tool as-is. And I am not qualified to review C++ :) If you find yourself on irc or matrix, my contacts are here. Good luck with your new job! |
@motiejus hi! Thanks! |
Now that inotify-info starts being included to distros, we (I) may need some "signal' when it' worthwhile to update it downstream.
I could follow all commits and arbitrarily decide when I feel like a "release" is worthy by taking a snapshot.
Or you may think "this is something that should end up downstream" and just cut & push a tag. That has a higher chance to have it consistent across distros, when there are more.
If ut wouldn't be too much to ask, it would be great if you could make a tag from time to time. Distro packagers will do the rest.
Feel free to close it and keep not making tags, I will just keep following the commits.
Thank you for the product!
The text was updated successfully, but these errors were encountered: