Release 3.0.0-beta.6

[xzyfer]

This is tracking the tasks required to release 3.0.0-beta.6

• bump libSass and sass-spec to 3.2.0-beta.6 (Release 3.0.0 beta.6 #872)
• build OSX binaries (Add OSX binaries for 3.0.0-beta.6 node-sass-binaries#58)
• build linux binaries
• build windows binaries
• mention known issue with Windows and iojs ("Module did not self-register"on Windows 8.1, iojs 1.7.1 #870)
• update readme to clarify that custom importers and functions are highly experimental (Clarify custom importers and functions are still experimental #878)

Optional

• build SmartOS binaries /cc @geekrohit @candid
• build FreeBSD binaries /cc @saper

@am11 @saper @geekrohit @candid could you please assist in creating the relevant binaries and PR'ing node-sass-binaries?

You can use sass/node-sass-binaries#58 as a template for said PR. We require binaries for node 0.10.latest, node 0.12.latest, iojs 1.0.0, iojs 1.7.1 on both 32 and 64 bit OSes. I recommend using nvm to manage the multiple node/iojs versions.

When this issue is closed 3.0.0-beta.6 will be released.

[xzyfer]

x-referencing #858 #713 sindresorhus/grunt-sass#203

[djensen47]

Out of curiosity, why are SmartOS and FreeBSD optional? Or is it just optional for Beta 6?

[Jakobud]

Just curios, why doesn't node-sass version numbers stay consistent with the libsass version that is used? For example if libsass is at 3.2 and node-sass using that version, shouldn't node-sass say it's also version 3.2? Just for consistency sake? I came to this issue because when I was looking at my version of node-sass I had installed I saw 3.0.0 and my first thought was "it's using libsass 3.0?".

[xzyfer]

Out of curiosity, why are SmartOS and FreeBSD optional? Or is it just optional for Beta 6?

@djensen47 for this beta, and potentially the initial stable release. I don't believe it makes sense (or fair?) to hold up a release waiting on FreeBSD or SmartOS binaries for a couple reasons.

• support for them is either very new or non-existent in current releases
• as a results using is on those OSes is small in comparison
• we don't currently have anyone owning the responsibility to build those binaries

Until we can automate the building of FreeBSD and SmartOS binaries, or someone volunteers to be responsible for doing so, it's hard to justify holding everyone else behind.

To be clear we can trivially add these binaries as soon as they become available.

If this is something you want to help with we're more than happy to make this a priority :)

[xzyfer]

why doesn't node-sass version numbers stay consistent with the libsass version that is used

@Jakobud these are two distinct projects. Node-sass adheres strictly to semver. We desire the freedom to make improvements or breaking changes to our user face API independent of libSass releases.

Our relationship to libSass is analogous to grunt-sass' or gulp-sass' relationship to node-sass.

[mgreter]

I fully agree with @xzyfer, as it would tightly couple the release cycles of both projects, and that is not what you want, neither as a developer nor as a consumer! I agree, try to keep it somewhat close if possible, but semver goes first!

[xzyfer]

We're currently waiting on @am11 to either building our linux binaries, or instruct me on his process. There is some complication around our linux binaries as we need to support relatively old distributions.

[xzyfer]

x-referencing #850

[rohit-saharan]

On it. Will see if I can setup a jenkins task to do this and push. What say @xzyfer ?

[xzyfer]

Push to what exactly @geekrohit?

Ideally we need SmartOS binaries for node 0.10.38, 0.12.0, iojs 1.0.4, 1.8.1 on both 64 and 32 bit. Binaries should be submitted as PR to https://github.com/sass/node-sass-binaries.

Here is a good template to follow sass/node-sass-binaries#58

I recommend using nsm to manage multiple node versions (if that's an option).

[xzyfer]

I will be spending considerable time on automating this process for the next minor release.
For now I'm keen to get this release out asap.

[rohit-saharan]

Yeah, will make a repo like that and submit for PR. Thats what I meant by using jenkins for doing that.

[xzyfer]

Oh ok, great. I currently use docker for as much as possible. I use a minor variation of this for building linux binaries - https://gist.github.com/am11/1529b2458b1a1f4bdba8

[saper]

Which commit should I base the FreeBSD ports on? Currently using 8b7ad43 for testing

[xzyfer]

I'll be creating the 3.0.0-beta.6 tag in minutes.

[frvge]

Very interested in the FreeBSD binaries here.

[chriseppstein]

👍

....

OMG I'm that guy.

[xzyfer]

This has been released as v3.0.0-beta.7.

There was an npm hiccup on publishing v3.0.0-beta.6 so I have unpublished. My fault.