Cut a new release before rspec 3.0.0.beta2 comes out about rspec-its

[palfvin]

@myronmarston Sure. I was thinking I need to do that, but wasn't sure what number to give it (not to mention having to figure out github tags, release mechanism, etc.). If I'm interpreting the history correctly, I think you gave it 1.0.0.pre initially. Under the circumstances (i.e. dead simplicity of the gem, maturity of RSpec 3.0), do you think this a reasonable time as any to use 1.0.0? If not, any other suggestions?

[myronmarston]

To cut a release, run bundle exec rake release after committing an update to the version in version.rb and the changelog. It'll take care of tagging it, pushings the tags, building the gem, pushing the gem to rubygems.org, etc.

I think 1.0.0 is fine.

[palfvin]

Just a couple of follow-up questions if you don't mind.

I did the release while on a branch that had only been committed and not pushed, let alone merged to master. After I did the release, I then merged to master locally and pushed up because I couldn't figure out how to do a "pull request" on github from the tagged version to master. Can you tell me the "normal" process for doing all that or point me to something to read?

Also, I failed to update the URL for "full changelog" link in Changelog.md since there was no way for me to test the new tag reference prior to creating the tag and was thinking (naively) that the release process might automatically update that. Is the convention to just update the URL with expectation that it will work after the tag is created?

[myronmarston]

Usually when I do the release I do it locally on my master branch, and then the git push performed by rake release pushes directly to the master branch on github.

As for changing the "full changelog" link -- you don't need that in the first place if you don't want it. It's your gem. Maintain it how you like. It is kinda nice to have the link, though. I know the tagging convention (e.g. v1.0.0), so I put that directly in the changelog link URL. You can always fix it after the fact. While the released gem will not have the correct link, people browse the github UI for the changelog more than dig through the released gem source, I think, so that's OK.