This mainly concerns consumers like node-sass ❗

As you probably know by now, we introduced a few new features and changes in the C-API with the fourth beta. Currently node-sass is catching up to support those features in its upcoming 3.0.0 release.

I labled the last beta 4 release "release candidate 1", since I'm commited to not introduce any more breaking changes in the C-API (with one exception, if it is obvious and trivial, like fixing typos in typedefs etc). So once implementors support the beta 4 release, it should only be a matter of pulling the latest master branch, once we tag/release the final libsass 3.2.0 version 🚀

@am11 It would be great if you could keep us posted when you plan to release the next beta for node-sass. We would like to do another beta release just before that, so you can include as many changes as available in the node-sass beta. At that point I propose to have a feature freeze and only add bugfixes. IMO we should not hold on for too long and release 3.2.0 after maybe a week or two (if not too many regressions appear)! I'd rather do a patch release quickly after 🪲

IMO there are already two interesting features in the pipeline by @onedayitwillmake and @xzyfer 👍