There are several issues that will be resolved once all dependencies are released to MELPA. I'm opening this issue to link the other issues together (and to close them all as duplicates of this core problem).
In the past, I haven't prioritized MELPA-Stable since I don't use it, but clearly a process should be created so folks who do use 'stable' versions aren't forgotten. I don't know what such a process would look like, yet -- a process made more difficult with functional dependencies on other projects continually enhanced with the needs of the present one in mind. I've considered adding a matrix variable to Travis CI testing, but I don't believe this will work well with the tags necessary to make MELPA-Stable work. (If I'm wrong, please let me know! This could be an ideal approach.)
There are several issues that will be resolved once all dependencies are released to MELPA. I'm opening this issue to link the other issues together (and to close them all as duplicates of this core problem).
In the past, I haven't prioritized MELPA-Stable since I don't use it, but clearly a process should be created so folks who do use 'stable' versions aren't forgotten. I don't know what such a process would look like, yet -- a process made more difficult with functional dependencies on other projects continually enhanced with the needs of the present one in mind. I've considered adding a matrix variable to Travis CI testing, but I don't believe this will work well with the tags necessary to make MELPA-Stable work. (If I'm wrong, please let me know! This could be an ideal approach.)