Node.js modules are supposed to use semver, and although I found that nobody really cares about putting incompatible changes in minor version, I wonder how it is supposed to be done right.
So, there is a question. What semver versions should be used when a certain library reaches 1.x.x version, but needs to fall back into initial development stage again? I'm talking about a development model similar to node.js core, when two branches are maintained, stable and unstable one, and no guarantees are provided for an unstable. Should it be something like this?: 1.0.0 1.0.1 ... 1.5.0 ... 2.0.0-pre1 2.0.0-pre2 ... 2.0.0-pre4096 ... 2.0.0 2.0.1 ... Is there a way out of browser versioning if such an iteration is just a few months long? :) Yeah, I've read the FAQ, and it isn't extremely convincing. -- -- 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.
