-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
@saper can you please get this up to date with sass/libsass@ab86285. This will likely be out next release. |
This is now updated. It looks like we are getting test failures here - most probably those are some fixed bugs? My slow VM tests on Windows bring even more failures - mostly timeouts though. |
(I just noticed I have used the current libsass master, not sass/libsass@ab86285 - but the |
Last commit does not work atm because I haven't told git how to |
830b450
to
884c508
Compare
With sass/libsass#1521 merged we can remove |
9ecb144
to
010205f
Compare
eef1db1
to
99a21e3
Compare
Moved ready-to-merge tests and libsass.gyp changes to #1146. Here is the actual layout change/import. |
eef1db1
to
99a21e3
Compare
99a21e3
to
4c08979
Compare
@@ -1,7 +1,7 @@ | |||
{ | |||
"name": "node-sass", | |||
"version": "3.3.2", | |||
"libsass": "3.2.5", | |||
"libsass": "3.3.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3.3.0-beta1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On Wed, 16 Sep 2015, Michael Mifsud wrote:
@@ -1,7 +1,7 @@
{
"name": "node-sass",
"version": "3.3.2",
- "libsass": "3.2.5",
- "libsass": "3.3.0",
3.3.0-beta1
We are already one merge above :)
We can adjust as we are close to merge this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to merge this now :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On Wed, 16 Sep 2015, Michael Mifsud wrote:
@@ -1,7 +1,7 @@
{
"name": "node-sass",
"version": "3.3.2",
- "libsass": "3.2.5",
- "libsass": "3.3.0",
I want to merge this now :)
Holy...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LibSass 3.3.0 can't go stable until atleast one RC has hit node-sass. This is because the vast majority of LibSass usage happens via node-sass and we use node-sass@beta release to weed out regressions.
More accurately, I want to release v3.3.3 with the changes currently on master. Then I want to release this as |
4c08979
to
84332a1
Compare
So we can ask our dear readers to re-test all https://github.com/sass/node-sass/milestones/next.libsass issues with |
At the very least. Once we let people know they can get their hands on the new super fast LibSass we'll see good rapid adoption. |
@saper I see that test failure randomly on Travis as well. This is good to go as far as I'm concerned. |
On Wed, 16 Sep 2015, Michael Mifsud wrote:
@saper I see that test failure randomly on Travis as well. This is good to go as far as I'm concerned.
I've been restarting Travis build pretty often. We need to do something about the file watching one day.
|
Agreed. Luckily Travis lets you build a single job and it only takes 2-3mins. |
eef1db1
to
84332a1
Compare
- New source layout - New header names for #include - No need for exception handling in pure C code
84332a1
to
3f0ef90
Compare
From now on, use includes from
src/libsass/include and the sources from
src/libsass/src
This is to be included when merging newer libsass.