May you please create a tag for release? about polymode

[vspinu]

This surely makes sense and I will do that once the first "stable" version of polymode is out. Unfortunately, as much as I would want it not be, it's still in development and very unstable outside R world.

[grettke]

Gotcha.

My vote is that the stable is really just a tag. So if you tag it at 0.0.N, then, we all get that it is still in development. It is just that, 0.0.N works perfectly for 0.0.N features, so, why not depend on them and nothing more.

[mdorman]

I would echo this---it doesn't have to be perfect, but it at least represents something someone else's package could, for instance, depend upon.

Maybe for the first one, like Grant said, just choose 0.0.0 and tag whatever's current, and then when there are pauses in development, just increment.

[vspinu]

I am actually very close to a refactored stable release (next branch). I don't think starting tagging this master branch is a good idea because it will surely create dependency confusion.

[vspinu]

The repo is tagged now but I would recommend using the master (MELPA) for time being as issues are fixed on a daily basis right now.

[grettke]

Gotcha. Thanks!