Time to ship 3.0.0?

[xzyfer]

We have a couple of breaking changes on master already, a couple more in the works.

I think we should ship vNext with the update sass binary paths (#695). This opinion in motivated largely due to the volume of io 1.3 issues and knowing that 1.4 is just around the corner.

[am11]

knowing that 1.4 is just around the corner.

Haha! That is so true.

I agree vNext should be 3.0.0 instead. I think we should wait for @matryo to finish #644.

Then I suggest we have alpha release, followed by beta and then RTW. This to nail out proxy related issue: #705 as well as the other planned for the vNext milestone.

@xzyfer did you have any luck with FreeBSD binary? I haven't tried it yet..

[xzyfer]

@xzyfer did you have any luck with FreeBSD binary? I haven't tried it yet..

honestly I haven't looked into it but I can try to make some time

I think we should wait for @matryo to finish #644.

Sounds good. I mostly wanted to emphasise there's not benefit in waiting for Libsass 3.2 before shipping these great updates. Libsass 3.2 is going to be a while off yet, partially because most of my time is taken up by CSSConf AU at the moment.

[xzyfer]

I'd also love to have #704 as part of vNext. This will help to ween people off this feature, and prevent the need for a 4.0 with Libsass@3.2 drops.

[xzyfer]

knowing that 1.4 is just around the corner

https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md#2015-02-26-version-141-rvagg

@am11 can you confirm that io js 1.4.1 is using the same version on v8 as 1.2?

[am11]

Yes! see the "four minutes ago" story appveyor/ci#147 (comment). 😃

[xzyfer]

Haha

[am11]

@am11 can you confirm that io js 1.4.1 is using the same version on v8 as 1.2?

Nah it is changed! :(

C:\Users\Adeel\Source\Repos\node-sass>nvmw use iojs-v1.0.0
Now using iojs v1.0.0

C:\Users\Adeel\Source\Repos\node-sass>node -p process.versions.v8
3.31.74.1

C:\Users\Adeel\Source\Repos\node-sass>nvmw use iojs-v1.1.0
Now using iojs v1.1.0

C:\Users\Adeel\Source\Repos\node-sass>node -p process.versions.v8
4.1.0.14

C:\Users\Adeel\Source\Repos\node-sass>nvmw use iojs-v1.2.0
Now using iojs v1.2.0

C:\Users\Adeel\Source\Repos\node-sass>node -p process.versions.v8
4.1.0.14

C:\Users\Adeel\Source\Repos\node-sass>nvmw use iojs-v1.3.0
Now using iojs v1.3.0

C:\Users\Adeel\Source\Repos\node-sass>node -p process.versions.v8
4.1.0.14

C:\Users\Adeel\Source\Repos\node-sass>nvmw use iojs-v1.4.1
Now using iojs v1.4.1

C:\Users\Adeel\Source\Repos\node-sass>node -p process.versions.v8
4.1.0.21

So what should be our course of action now, only support the latest io.js version?
The idea was to release for latest version of io.js and node.js; and (latest - 1) stable-version of node.js.

PS: v8 does not seem to use semantic versioning..

[mgreter]

@am11 are you sure you cannot just discharge the last digit from v8 verson (you still have 4.1.0, which IMO is exactly semantic versioning).

[am11]

@mgreter, you are right! I thought v8 folks just do not use sem versioning at all. 😸

The binary that was built with iojs v1.1.0 is working with 1.2.0, 1.3.0 and 1.4.0. Which means we need to strip off the last slug from the version (I guess that is a build number in their modified versioning scheme?)

However, the same binary does not work with the first (stable) io.js 1.0.0: Error: Module version mismatch. Expected 42, got 43..