The official release is still 0.6.1c. There is *no* official 0.7 or 0.8 release.
I just tag the files that way as I go along. I also keep pushing the 0.7 milestone when I start hitting the deadlines. From then on, as people start finding bugs, I have been increasingly advising people to use the "trunk". I wish I could do a better job of making releases but YASnippet but there is work to be done in testing and documentation (of which the changelog is a part) before that release happens. If I make a release sooner without these two I will get flooded by questions and bug reports that I cannot answer timely.
Additionally, YASnippet has recently been assigned to the FSF, and the Emacs maintainers requested some fairly substantial changes (like renaming all "yas/*" symbols "yas-*"). That has lead me to bump the version to 0.8, so the next version (and the one included by Emacs in the official
elpa.gnu.org repository) will hopefully be 0.8.
You are however completely right to note there has been little investment by me in making releases and/or updating the documentation. This is clearly undesirable but in general there is little that has stopped working since 0.6.1c, the exceptions being:
* generation of "yasnippet-bundle.el" files has been removed.
* hierarchical snippet dirs are no longer supported
* yas/find-snippets no longer exists (but maybe I'll bring it back)
A decent amount of new features, some still incomplete and discussed briefly in this mailing list and in the issue trackers, have not at all been documented:
* snippet-commands
* just-in-time loading
* yas-compile-all and yas-compile-directory
* yas-describe-tables
* yas-define-menu
* textmate-import.rb
These have been internal changes
* refactorings
* bug fixes
* polishing existing features
* automatic tests (still need many more)
The main goal now is documentation. The old documentation is sometimes confusing, porrly written, and does not conform to the standard emacs documentation format (texinfo). So the main goals are now:
1) Write it in a new format (preferably .org or .texinfo)
2) Write it in such a way that it reuses the emacs-lisp docstrings for symbols when possible, so I don't have to update it in two places.
3) Write it in one file
4) Revise it from a user perspective (I get suprisingly little feedback regarding usability of yasnippet)
5) Document the new features
In this case I need someone with good English skills and willing to coordinate with me by email. Emacs-lisp skills would be great for 2). If you're feeling up to it, do these changes in a github fork of the new "0.8-fsf-changes" branch (but send me email first). If not, you can already help superbly just by compiling up a list of new features and changes from the commit messages, mailing list and issue trackers.
In general I am always looking for help. YASnippet is quite popular and full of features, but it is also complicated and I have limited time to dedicate to it. I get some offers to help with new features (and a million pull requests for snippets) but not a lot for fixing bugs, writing automated tests, performing good old maintenance work, or even strategic discussion of where YASnippet is headed.
João