Skip to content

Conversation

@mx4492
Copy link

@mx4492 mx4492 commented Feb 26, 2015

Now you can do gem install git-game.

@mx4492
Copy link
Author

mx4492 commented Feb 26, 2015

@jsomers If you provide me with the email address for your rubygems.org account, I'll add you as a owner.

@ayushgoel
Copy link

Nice 👍
Thanks!

@jsomers
Copy link
Owner

jsomers commented Feb 28, 2015

@mx4492 This is sick! Rubygems account email is my github handle at gmail.

Would you mind fixing merge conflicts on this as well? (I'm sure they're trivial.)

Also, is there any relationship between the version given in the gemspec and the GitHub release version number? If so, I've now bumped it to 1.2. Thanks!

@mx4492
Copy link
Author

mx4492 commented Mar 1, 2015

Fixed the conflicts.

I've added you as an owner. Since you've already pushed the 1.2 tag to Github, it would be incorrect to push a new gem with the same version number but different source, so I suggest that you skip 1.2 for Rubygems and instead release a new version 1.3 (on both Github and Rubygems) once this is merged.

Also, is there any relationship between the version given in the gemspec and the GitHub release version number?

No. There isn't. However, if you have bundler installed on your system, then there is a handy rake task to ensure that they remain in sync. I've listed the steps to release a new version in the Development.md file in this PR (I can revert that commit if you think documenting these steps is unnecessary).

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

Successfully merging this pull request may close these issues.

4 participants