In the TC meeting today we came up with a vision for the first release.

First, a few assumptions we've internalized that probably need to be stated for this to make sense.

• Node is pretty damn stable already. There are huge companies with it in production, 100K+ modules, etc. It is already far more stable that its pre-1.0 release tag suggests.
• Releasing more frequently leads to a more stable product, not a less stable product.
• The entire ecosystem uses semver while node uses a confusing even/odd release structure.

If people disagree with any of those assumptions then they certainly won't agree with anything the TC determined for the initial release.

So, first release of io.js:

• January 13th (Fedor's Birthday!) target date.
• Will be 1.0-alpha1, with alpha releases continuing until 1.0.0.
• Switching to semver.
• We will be taking new v8 releases as fast as possible moving forward.
• Trying to get to a weekly release cycle. Which version number is incremented each week is determined by the changes and whether or not they are breaking. Again, following semver.

Some questions still left open:

• Are there any changes other than dep upgrades and fixes required for 1.0?
• Is build confident we can have enough automation in place to hit this date.
• Is the plan to have the installer install an iojs binary and an alias to node?