Release a new version

[paulmelnikow]

Hi there,

Would you mind tagging a new release? It looks like the last one was in 2008 so it's missing a bunch of commits.

At the moment, I'm hung up on the fact that the last tagged release has no package.json.

Thanks!

[jcoglan]

I can't do that easily at the moment. Basically, a few years ago someone took my half-finished work, added a bunch more code and tests (that I can't find anywhere on github), and published it on npm. In order to make a viable release, I need to merge this codebase (which I was intending to release as 0.2 before handing off to other maintainers) with that fork, incorporate the tests, respond to a huge backlog of issues, clean various things up and get the project back into a maintainable state, so I can make a release that won't break downstream code.

Due to various other projects, I've not had time to work on this for years and it only keeps getting harder for me to dedicate time to moving it forward.

[paulmelnikow]

Ah, okay, understood. I was hoping to work off this codebase but it looks like I need to work off a fork for the moment.

By the way, this is the repository for the version that's in NPM: https://github.com/NaturalNode/node-sylvester