Time ago I wrote my modules to suppot node 0.6 and 0.8, but that's stupid. Some reasons I don't support older versions:
- You need to patch bugs. - v0.x means unstable, under active development, a lot of thing could change. From semver <http://semver.org/>: Major version zero (0.y.z) is for initial development. Anything may change > at any time. The public API should not be considered stable. - The only way you can see which bugs or changes you must now is looking to the changelog. Good luck. - I'm too lazy to rewrite and retest my code. Update node or gtfo :). El miércoles, 7 de agosto de 2013 17:25:52 UTC+2, Bart escribió: > > I'm developing some modules and wondered if support for node.js 0.6 is > still worth investing time in. > > Let's focus on projects where new features are still being added or major > re-factoring is being performed (and not active legacy projects that are > not likely to add new dependencies). > > And what about 0.8? For the level of things I write 0.8 is easy enough to > support but is it worth it? > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
