-
-
Notifications
You must be signed in to change notification settings - Fork 135
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 Version Naming #92
Comments
Hm, sounds reasonable. The next release I make (there might be a point release in the next couple weeks) will probably be like (I'll keep this open until my next release so I don't forget) |
Sounds like a plan, thanks. I would say if you do a point release then go with Tracking upstream's version is definitely helpful, but depending on how much changes it may start to lose its meaning so I can see either way there. |
Yeah, definitely. I've been super on the fence about keeping the version numbers in-line with upstream - on the one hand, it's handy to tell if I've merged upstream's latest stuff yet, but on the other hand, it becomes kinda a pain to make i3lock-color releases that aren't related to upstream releases (and I want to avoid future naming conflicts, so just appending a -c seemed the easiest at the time... oops) |
Note the change in naming scheme, this is intentional (Raymo111/i3lock-color#92)
Note the change in naming scheme, this is intentional (Raymo111/i3lock-color#92)
Fixed in the latest release. Sorry about the delay in release; my internship this summer kept me tired & busy. |
Would it be possible to modify the release naming template going forward? Hyphens are incompatible with rpms/debs. Maybe something like
2.11.c
instead of2.11-c
?The text was updated successfully, but these errors were encountered: