Scalding 0.17.2 release

[ttim]

0.17.2 release reverts backward incompatible estimators change and is backward compatible with 0.17.0.

In this PR I've set version to 0.17.2 and added changes to CHANGES.md file. Once merged I'm going to publish jars and tag this commit as 0.17.2 release. After that I'm going to set version to 0.17.2-SNAPSHOT and cherry-pick this PR in develop branch as well.

I've tried to use git flow but looks like it doesn't work if you do release not from develop branch.

@piyushnarang @johnynek are you ok with this?

[johnynek]

I don't think we need to cherry pick this commit in develop so we?

After we publish we need to set Mima to compare to 0.17.2 and I think the version should be 0.17.3-SNAPSHOT. Snapshots should precede the version they represent not follow.

[ttim]

@johnynek I guess we should cherry-pick changes from CHANGES.md.
Version will be 0.17.3 - you are right, actually I was wondering about this.
About mima - yes, you are right here as well, will do after release. Do you think we need separate PRs for that or it's just part of release process so I can just commit this as is?

[piyushnarang]

Yeah it would be nice to have the changes.md updated on develop. We missed that the last couple of times as we've just been updating the rel notes on github.

[piyushnarang]

Also @ttim you can use the sbt release plugin. I believe that's what @tonyzhoujingtao used for the 0.17.1 release.

[johnynek]

We need to document the steps (I thought we had done that) and maybe even automate more, if they exist, using `sbt-release`

…

On Fri, Jul 14, 2017 at 7:29 AM, Piyush Narang ***@***.***> wrote: Also @ttim <https://github.com/ttim> you can use the sbt release plugin. I believe that's what @tonyzhoujingtao <https://github.com/tonyzhoujingtao> used for the 0.17.1 release. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1707 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEJdgJPmhBt7vJupRskEZozbYo39pkFks5sN6V3gaJpZM4OX0JT> .

-- P. Oscar Boykin, Ph.D. | http://twitter.com/posco | http://pobox.com/~boykin

[ttim]

@johnynek @piyushnarang Will use sbt-release. I've updated our internal doc to reflect usage of sbt-release only for scalding.

I've found couple of places with version which should be updated.

If everyone is agree I'm going to merge this PR and do 0.17.2 release.

[johnynek]

we should automate this: we could have the build create a file and we could import that file to get the version (I have seen people do something similar for the git-sha which would also be nice.

[johnynek]

👍

we should probably make a script that does sed on the an old version to a new version so we don't always have these issues.