-
Notifications
You must be signed in to change notification settings - Fork 20
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 a new version #169
Comments
+1 :) |
👍 |
I actually foked primus just so I could do version bumps after testing the updates for my slackware users. |
On arch and ubuntu we use yyyymmdd-n release version number. This is easy to use. You can also use rev number, and in both case, at git short commit number to specify the release. Normally, we release after each serie of change, since @amonakov works this way. |
@ArchangeGabriel I know that is a common practice, but I think that tagging version make more maintainable the software repositories. Moreover I'm asking because the project already have a tag (0.1) but it is 2 years old. |
Well, once @amonakov will have shown signs of life, maybe he will consider merging pending patches and potentially tag a 1.0 or 1.1 version (because of Fedora version numbers) if needed. |
0.2 was just tagged! |
Yep, in a conversation @zx2c4 convinced me to just tag current tree with v0.2 since he wanted to put primus ebuild upstream in Gentoo (which he has just done). Sorry about not taking care of the pending pull request, but I'll try to merge that before the next tag ;) |
Version is tagged (0.2): see #190. issue can be closed OK. |
Hi,
First of all thank you for your work, I like very much this project.
I'm here to ask if could be possible to tag a new version of primus, because the last tag is really old and last commits works well i think.
Best Regards.
The text was updated successfully, but these errors were encountered: