Tag and release a version

[singingwolfboy]

I would like to package this project in Homebrew, and that requires a publicly released version of the project. I already wrote the formula file, so it should be pretty easy to get this merged once we have a published version!

[blm768]

The only problem with that is that I wouldn't consider this ready for release. In particular, there's an existing issue with collation (#3) that, as far as I'm aware, would be difficult to change in a backwards-compatible way because any changes would cause issues with existing column indices, so it's fairly important that I get it right the first time. I can try to look into that sometime in the next couple of weeks, though.

[singingwolfboy]

You can still tag the codebase with a pre-1.0 version, to indicate that the project is not yet stable and will have backwards-incompatible changes. Seems like you've already marked it as version 0.1.0 -- that would work just fine. Just needs a tag on GitHub.

[blm768]

By my reading of the Homebrew package guidelines, they really seem to want a tagged stable version, not just any tagged version, and until the existing issues are resolved, I really can't call this project stable. I'm planning to try to iron those out over the next few weeks and at least get something minimally feature-complete. In the meantime, would creating a custom tap work as an interim solution for your own development purposes?