Bring the Node.js fork up to date?

1 view
Skip to first unread message

Michael Morrison

unread,
Apr 9, 2013, 5:51:19 AM4/9/13
to node-...@googlegroups.com
It may be an appropriate time to rebase the nodejs branch, now that we're rebasing chromium. The nodejs in node-webkit is nearly a year out of date.

-- Michael

Roger

unread,
Apr 9, 2013, 7:11:32 AM4/9/13
to node-...@googlegroups.com
The plan was to rebase Node in 0.5.0, but it cannot be done in the time frame due to bigger changes than expected (libuv). So we'll do it in some next version.

btw, is there any strong need to use Node v0.10 rather than v0.8?

Roger


On Tue, Apr 9, 2013 at 5:51 PM, Michael Morrison <di...@sonicsnes.net> wrote:
It may be an appropriate time to rebase the nodejs branch, now that we're rebasing chromium. The nodejs in node-webkit is nearly a year out of date.

-- Michael

--
You received this message because you are subscribed to the Google Groups "node-webkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Esa-Matti Suuronen

unread,
Apr 9, 2013, 7:14:56 AM4/9/13
to node-...@googlegroups.com
On Tue, Apr 9, 2013 at 2:11 PM, Roger <wen...@gmail.com> wrote:
> btw, is there any strong need to use Node v0.10 rather than v0.8?

Streams are pretty awesome in 0.10 (although they can be backported to 0.8)


--
Esa-Matti Suuronen
esa-...@suuronen.org
http://esa-matti.suuronen.org

Philippe Jean

unread,
Apr 9, 2013, 8:59:06 AM4/9/13
to node-...@googlegroups.com
0.10 has a lot of improvement, among which stream and bug fixes in socket and http hangout….
philippe 

Yongkang You

unread,
Apr 9, 2013, 11:35:35 AM4/9/13
to node-...@googlegroups.com
0.5.0 already slipped its schedule. If it is too risky to backport to node.js 0.10 in a short time (especially for the libuv changes), I would prefer to postpone it to next release. So people could use new node-webkit earlier, since we already have some good features and merged with latest Chromium and WebKit.
Yongkang You

Chris Granger

unread,
Apr 9, 2013, 11:40:21 AM4/9/13
to node-...@googlegroups.com
I agree, it'd be better to just get 0.5 out for now so we can take advantage of all the nice improvements there. :) That being said, it would be nice if node could get bumped up in the not too distant future - I've definitely run into some bugs in node that seem to be fixed in more recent versions.

Cheers,
Chris.

piou...@gmail.com

unread,
Apr 15, 2013, 7:37:55 AM4/15/13
to node-...@googlegroups.com
+1

Roger

unread,
Apr 25, 2013, 2:18:11 AM4/25/13
to node-...@googlegroups.com
The rebase to Node v0.10.5 is done in git. It will be released in 0.5.1 soon.

Chris Granger

unread,
Apr 25, 2013, 11:34:32 AM4/25/13
to node-...@googlegroups.com
@Roger that's great! Any idea when you're going to release binaries for 0.5.1? I'd love to use those for the release I'm doing early next week. :)

Cheers,
Chris.


On Wed, Apr 24, 2013 at 11:18 PM, Roger <wen...@gmail.com> wrote:
The rebase to Node v0.10.5 is done in git. It will be released in 0.5.1 soon.

Roger

unread,
Apr 25, 2013, 8:52:10 PM4/25/13
to node-...@googlegroups.com
It is planned to be released this week, after the fix for #663 and
'nwfaketop' fully functional in #534

https://github.com/rogerwang/node-webkit/issues/534
https://github.com/rogerwang/node-webkit/issues/663

Roger

damien...@gmail.com

unread,
Apr 27, 2013, 12:28:21 PM4/27/13
to node-...@googlegroups.com
I've just tried it, and it works like a charm.

Thank again Roger !
Reply all
Reply to author
Forward
0 new messages