Stable version outlook (0.5.0)

[RyanMcG]

Any idea when a stable version of stefon will be released?

Not sure if this is the best way to ask the question but I figured it'd work.

[pbiggar]

The plan had been to do it after finishing these features: https://github.com/circleci/stefon#planned-before-release

[RyanMcG]

Great, thanks for pointing that out. I am a bit confused about how stefon would handle markdown preprocessing or why. While they seem quite similar asset preprocessing and generation of static HTML from sources like markdown have always had different solutions.

What are your thoughts on it?

[RyanMcG]

I should also add that an updated SNAPSHOT release of current HEAD would be helpful even thought it is not a stable release.

[pbiggar]

@RyanMcG markdown would be the same as currently - generating HTML or similar from markdown files.

I should point out that we don't need to ship all the things in that list. We could just call it a day here and improve the others on the next release.

I don't like SNAPSHOT releases, but don't mind sha1 releases.

[RyanMcG]

I don't like SNAPSHOT releases, but don't mind sha1 releases.

Fair enough. They are a bit more explicit.

I should point out that we don't need to ship all the things in that list. We could just call it a day here and improve the others on the next release.

It is entirely up to you. Releasing now/soon might help me out a little bit, but it is not my call, especially if you are really hoping for one of those features first.

the same as currently - generating HTML or similar from markdown files.

To my knowledge the only assets stefon is dealing with currently are those which are requested from an HTML page (CSS and JavaScript).

I suppose certain one-page-apps might benefit from that sort of thing though (dynamically loading HTML content) but I am having trouble coming up with other use cases. Do you have one in mind? I am not arguing against a markdown asset parser, I just don't know how I'd use it.

[RyanMcG]

I don't like SNAPSHOT releases, but don't mind sha1 releases.

I've been looking around to figure a good way to do this. Do you have a particular method. So far I have come up with: temporarily modify project.clj to use the current git commit's sha1.

[pbiggar]

That's the way I tend to do it, yeah.