Publishing, versioning

[johnynek]

I was thinking it might be good to publish a series of releases (0.0.x) and make branches of algebird and spire that pull those jars. We might turn up some issues at that that point and want to make quick fixes.

I think when we have versions of 0.0.x that compile for both Spire and Algebird, we could publish 0.1.0 and then publish new versions of Algebird and Spire to use those.

Next, it would be great to use Mima to enforce no binary incompatibilities between x.y.z and x.y.z'. We struggled with binary incompatibility issues for a long time until we got more rigorous about such testing. Recently, on the x.y develop branches have mima running as part of the travis tests so we can introduce breaks when there should be minor improvements.

[non]

This is a great idea.

How hard is it to set up Mima? Is this something you could contribute from another project? I think @larsrh also has experience here.

[non]

(Unfortunately I think I already published 0.1.0 awhile ago, so we may need to start with a different version.)

[johnynek]

Happy to add mima setup when we have a stable artifact to test against.

[larsrh]

@johnynek We could also use sbt-typelevel for that, because it sets up MiMa automatically depending on whether the active branch is stable or unstable.

[non]

That sounds good. @larsrh how hard is it to deploy the plugin? Is it something I can just include? How much configuration is necessary?

[larsrh]

Not much. It requires little more setup than sbt-release. There's still an open bug in it, so "not yet", but I'll fix it in time for the next relevant release :-)

[sritchie]

Can we close this as well?