Nothing jumps out at me as significant to bump the version to 0.9. Can someone explain what makes certain changes worthy of the version change?
Node.js v0.9.0 (Unstable) is out
11–16 of 16 posts
Re: Node.js v0.9.0 (Unstable) is out
#12Nothing jumps out at me as significant to bump the version to 0.9. Can someone explain what makes certain changes worthy of the version change?
Node follows a even/odd version scheme where even releases are stable and odd releases are unstable. v0.9.0 is just the first release of the unstable v0.9 series.
The versioning scheme is unfortunate because it confuses people. After Node 1.0 we'll switch a less confusing version system.
Re: Node.js v0.9.0 (Unstable) is out
#13Nothing jumps out at me as significant to bump the version to 0.9. Can someone explain what makes certain changes worthy of the version change?
Node follows a even/odd version scheme where even releases are stable and odd releases are unstable. v0.9.0 is just the first release of the unstable v0.9 series. The versioning scheme is unfortunate because it confuses people. After Node 1.0 we'll switch a less confusing version system.
Is it not standard semver? What will node switch to?
Re: Node.js v0.9.0 (Unstable) is out
#14Earlier quoted context omitted.
Node follows a even/odd version scheme where even releases are stable and odd releases are unstable. v0.9.0 is just the first release of the unstable v0.9 series. The versioning scheme is unfortunate because it confuses people. After Node 1.0 we'll switch a less confusing version system.
Is it not standard semver? What will node switch to?
isaac likes semver - so probably that
Re: Node.js v0.9.0 (Unstable) is out
#15I haven't even finalized migrating from 0.4 to 0.8...
Re: Node.js v0.9.0 (Unstable) is out
#16Earlier quoted context omitted.
Or it might be the unstable version of 0.10. The dots are there for a reason.
IMHO, it should be followed by 0.12, because 0.10 is too confusable with 0.1, but 0.12 is clearly a new version...
They use a variation on semantic versioning, which is pretty standard:
major.minor.revision
minor is incremented when backwards compatible features are added
major is incremented when backwards incompatible change is introduced.
All of them are integers, and the smaller ones are reset to 0 when a bigger one is incremented.
For versions 0.x.x (pre v1), backwards incompatible changes are allowed at any time.
There are more rules, see http://semver.org/