Tagging releases

[gslowikowski]

Tag every release, please.

[schmitch]

currently this should work now, the first releases were probably untagged since sbt-release was not configured.

[gslowikowski]

Can you manually create tags for previous releases?

[schmitch]

well I don't know the actual commits, and they were probably just milestones. maybe @wsargent knows them and can do that?

[marcospereira]

We still have some configurations to do, see #92.

The tagging step is not working correctly, at least no tag was pushed for M6.

[wsargent]

Getting sbt-release to actually work has been non-trivial. If someone can lend a hand that would be nice...

[gmethvin]

So, I did the last release (1.0.0-M6), and it turns out sbt-release created the tag locally but it didn't get pushed to remote. A git push --tags fixed that. So this seems like this a possible bug in sbt-release.

[gslowikowski]

The last question in release process is "Push changes to the remote repository (y/n)? [y]". If you answer "yes" pushChanges step is performed. It calls VCS (Git in this case) pushChanges method and it should push tags.

BTW I always answer "no" to the question and push changes manually after successful release (when I see new artifacts in Maven central repo).

[marcospereira]

@wsargent was this fixed by #106 and #107?

[wsargent]

Yes 😄