Skip to content
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

Open
dgikiller opened this issue May 12, 2015 · 9 comments
Open

Tag a new version #169

dgikiller opened this issue May 12, 2015 · 9 comments

Comments

@dgikiller
Copy link

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.

@akien-mga
Copy link

+1 :)

@mudler
Copy link

mudler commented May 12, 2015

👍

@WhiteWolf1776
Copy link

I actually foked primus just so I could do version bumps after testing the updates for my slackware users.

@ArchangeGabriel
Copy link

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.

@dgikiller
Copy link
Author

@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.

@ArchangeGabriel
Copy link

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.

@zx2c4
Copy link

zx2c4 commented Oct 16, 2016

0.2 was just tagged!

@amonakov
Copy link
Owner

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 ;)

@melroy89
Copy link

Version is tagged (0.2): see #190. issue can be closed OK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants