Pleas make a stable release about markdown-mode HOT 11 CLOSED

Oops, bad command line foo. Only 78 commits. Still, please make a stable release every few years ;).

from markdown-mode.

This has been on my mind too. I'd feel best about a release after some of the list filling issues (e.g., #16) are resolved.

from markdown-mode.

you can also tag v2.0: (on tag a3f710d)

from markdown-mode.

The 2.0 release happened before I started mirroring the repository on GitHub (but I didn't sync all the tags): http://jblevins.org/git/markdown-mode.git/tag/?id=v2.0

I pushed all of the previous version tags, including v2.0, to GitHub just now.

Version 2.1 is coming soon. It would be helpful if people can test the current master branch a bit to make sure it's stable.

from markdown-mode.

Do you want I set up test infrastructure with cask and https://github.com/AdrieanKhisbe/cask-package-toolset.el?

from markdown-mode.

Thanks to @syohex, we already have automated tests set up with Travis-CI. It seems to be working well so far. (What I meant above is real-world testing of things that may not be covered by the test suite.)

from markdown-mode.

Yep I saw. he already did made a good job :)
what I was proposing to add was to adapt ert-runner conventions test,
setup coverage stats with undercover, and add cucumber tests structure with ecukes

from markdown-mode.

markdown-mode 2.1 (release notes)

from markdown-mode.

@AdrieanKhisbe Thanks for generously offering to set these up. After thinking and reading about it quite a bit, I'm pretty content with what we have currently. I like that anyone can clone the repository and run the tests, exactly as I do, without outside dependencies.

If you have thoughts on how to make the existing test framework more transparent, let me know. (With 2.1 released I'll be closing this issue, but feel free to open a new issue or PR.) For example, it might make sense to move the Makefile to the root directory so that the testing process is simply make test instead of make -C tests test or cd tests; make test (the main reason I haven't is that I don't want to break existing workflows).

from markdown-mode.

great for the releases !! 👏

With Cask, you are set in just a cask install && make test :)

What do you mean by more transparent?

from markdown-mode.

What do you mean by more transparent?

More standard, or more easily discoverable by new contributors. I read that this was one of the main motivations for Cask.

from markdown-mode.