Friendly Reminder: Move Code to v0.3

[Ryan Dahl]

In the next week we will be releasing the next stable branch v0.4.

v0.4, like v0.2, will offer JavaScript, C++, and binary interface stability.

Please begin moving your code to v0.3.

Update this Wiki page with any troubles:
https://github.com/ry/node/wiki/Migrating-from-v0.2-to-v0.3

[Mikeal Rogers]

The registry (http://search.npmjs.org/) shows that these libraries are highly depended on (more than 15 other modules depend on them):

underscore
connect
request
vows
express
joose
coffee-script
test
colors
jsdom

Can we get updates from these library authors on their status and when they'll be compatible?

I'm working this week on getting request working with master, should be done by the end of the week.

[Dav Glass]

jsdom should be ready, I've been making sure that YUI 3 runs on the
latest and it makes pretty heavy use of JSDom at them moment..

Dav

--
Dav Glass
davg...@gmail.com
blog.davglass.com

+ Windows: n. - The most successful computer virus, ever. +
+ A computer without a Microsoft operating system is like a dog
    without bricks tied to its head +
+ A Microsoft Certified Systems Engineer is to computing what a
   McDonalds Certified Food Specialist is to fine cuisine  +

> --
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en.
>

[Matt Freeman]

I wouldnt have thought underscore took any direct dependencies on
node. last i look there was something to check if modules.export
exists and use that but apart from that? [disclaimer: not looked
recently]

[jashkenas]

On Jan 31, 10:05 pm, Matt Freeman <mattdrinksb...@gmail.com> wrote:
> I wouldnt have thought underscore took any direct dependencies on
> node.

Yessir, Underscore.js is just a plain JavaScript module, and works
fine under 0.3.7, without updates.

I've just released CoffeeScript 1.0.1 (also on that list), which fixes
compatibility with 0.3.7 as well. The only change that needed to be
made was with the REPL, readline.createInterface now takes three
arguments, where it used to only take two.

-- Jeremy

[Ryan Dahl]

On Mon, Jan 31, 2011 at 7:59 PM, jashkenas <jash...@gmail.com> wrote:
> The only change that needed to be
> made was with the REPL, readline.createInterface now takes three
> arguments, where it used to only take two.

Thanks. I updated
https://github.com/ry/node/wiki/Migrating-from-v0.2-to-v0.3 with that
note.

[Tim Caswell]

I know TJ has plans to rewrite Connect soon.  Also, since Stack is more recent work, it's compatible with 0.2.x and 0.3.x.  It uses the same middle-ware format as Connect, so may help ease the transition if the rewrite takes a while.

--

[Guido Tapia]

Any news on cygwin support for v0.4?

Any progress on plans for native windows install?

[Oleg Efimov (Sannis)]

Ryan, what about (Fast)Buffers/SlowBuffers fate in v0.4?

[Ryan Dahl]

On Mon, Jan 31, 2011 at 10:27 PM, Guido Tapia <guido...@gmail.com> wrote:
> Any news on cygwin support for v0.4?

I'll port cygwin.

> Any progress on plans for native windows install?

Yes, head builds under mingw.

[Ryan Dahl]

On Tue, Feb 1, 2011 at 6:51 AM, Oleg Efimov (Sannis) <efim...@gmail.com> wrote:
> Ryan, what about (Fast)Buffers/SlowBuffers fate in v0.4?

It landed months ago.

[Oleg Efimov (Sannis)]

Thanks for quick answer. Yes, I see. I mean, should you remove Slowbuffer or it will exist in v0.4.

[Guido Tapia]

Hi Ryan,

Great to hear the windows news. I tried building under mingw but got
the following error. I followed the instructions here:
https://github.com/ry/node/wiki/Building-node.js-on-mingw

Only changing this line:
./configure --without-ssl
to
./configure --without-ssl --prefix=~/dev/lib/node_ming

Thanks

Error.

[58/73] cxx: src\node_net.cc -> build\default\src\node_net_4.o
C:\MinGW\bin\g++.exe -m32 -g -O3 -DCARES_STATICLIB=1 -
DEV_FORK_ENABLE=0 -DEV_EMBED_ENABLE=0 -DEV_MULTIPLICITY=0 -
DX_STACKSIZE=65536 -D_LARGEFILE_SOURCE -D_FILE_
OFFSET_BITS=64 -DEV_MULTIPLICITY=0 -DFD_SETSIZE=1024 -
DHAVE_FDATASYNC=0 -DPLATFORM="win32" -Wno-unused-parameter -
D_FORTIFY_SOURCE=2 -DNDEBUG -Idefault\src -I..
\src -Idefault\deps\libeio -I..\deps\libeio -Idefault\deps\http_parser
-I..\deps\http_parser -Idefault\deps\v8\include -I..\deps\v8\include -
Idefault\deps\libev
-I..\deps\libev -Idefault\deps\c-ares -I..\deps\c-ares -Idefault\deps
\c-ares\win32-ia32 -I..\deps\c-ares\win32-ia32 -Ideps/v8/include ..\src
\node_net.cc -c -o
default\src\node_net_4.o

..\src\node_net.cc: In function 'v8::Handle<v8::Value>
node::SetMulticastTTL(const v8::Arguments&)':
..\src\node_net.cc:1424:53: error: invalid conversion from 'void*' to
'const char*'
..\src\node_net.cc:1424:53: error: initializing argument 4 of 'int
setsockopt(SOCKET, int, int, const char*, int)'
..\src\node_net.cc: In function 'v8::Handle<v8::Value>
node::SetMulticastLoopback(const v8::Arguments&)':
..\src\node_net.cc:1441:51: error: invalid conversion from 'void*' to
'const char*'
..\src\node_net.cc:1441:51: error: initializing argument 4 of 'int
setsockopt(SOCKET, int, int, const char*, int)'
..\src\node_net.cc: In function 'v8::Handle<v8::Value>
node::SetMembership(const v8::Arguments&, int)':
..\src\node_net.cc:1482:49: error: invalid conversion from 'void*' to
'const char*'
..\src\node_net.cc:1482:49: error: initializing argument 4 of 'int
setsockopt(SOCKET, int, int, const char*, int)'

Waf: Leaving directory `c:\dev\Tools\cygwin\home\guidot\dev\lib
\node_mingw\build'
Build failed: -> task failed (err #1):
{task: cxx node_net.cc -> node_net_4.o}
make: *** [program] Error 1

[Joe Thomas]

Use -fpermissive to downgrade those invalid conversion errors to
warnings.

[aaronblohowiak]

Is anyone successfully running connect-auth with Github-based OAuth on
0.3 branch? I am running into an infinite redirect loop that i'd
rather not debug if someone else has already fixed the issue. the same
code runs fine on 0.2.5.

Ta,

Aaron

[Ryan Dahl]

On Tue, Feb 1, 2011 at 10:26 PM, aaronblohowiak
<aaron.b...@gmail.com> wrote:
> Is anyone successfully running connect-auth with Github-based OAuth on
> 0.3  branch?  I am running into an infinite redirect loop that i'd
> rather not debug if someone else has already fixed the issue. the same
> code runs fine on 0.2.5.

Aaron,

Can you please report the issue on this wiki page:
https://github.com/ry/node/wiki/Migrating-from-v0.2-to-v0.3

[Laurie Harper]

Quick question on this: can npm manage multiple Node versions too? As in, "npm activate node@0.3" or something? I'd like to move to 0.3, but still easily be able to test modules for backward-compatibility.

No biggie if npm doesn't do that, I'm just trying to save a few minutes writing a shell script ;-)

[arlolra]

laurie, i think you're looking for something like this

https://github.com/isaacs/nave

[Qing Guan]

On 2 February 2011 16:56, arlolra <arl...@gmail.com> wrote:

laurie, i think you're looking for something like this

https://github.com/isaacs/nave

--

You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.

you can try this module https://github.com/kuno/neco, too. 

The author is me ;)

[Ryan Gahl]

One more (mentioned in the README for nave also): I use nvm https://github.com/creationix/nvm

[francisco treacy]

And one more, "TJ-style": https://github.com/visionmedia/n

2011/2/2 Ryan Gahl <ryan...@gmail.com>:

[Isaac Schlueter]

Managing multiple versions of node is an extremely oversolved problem.
The real question is whether you want me, TJ, Qing, or Tim to provide
support for the util you use.

popularitycontest++
v8bot: isaacs has given a beer to popularitycontest.
popularitycontest now has 1 beers.

--i

[Ryan Gahl]

On Wed, Feb 2, 2011 at 1:41 PM, Isaac Schlueter <i...@izs.me> wrote:

Managing multiple versions of node is an extremely oversolved problem.
 The real question is whether you want me, TJ, Qing, or Tim to provide
support for the util you use.

popularitycontest++
v8bot:  isaacs has given a beer to popularitycontest.
popularitycontest now has 1 beers.

-1

It wasn't a popularity contest, but rather a "in case you weren't aware of these other options" sub-thread. I think either you're too close to the ecosystem and thus assume everyone already knows about all alternatives to these things, or you perceived it as a popularity contest because you're an author of one of the mentioned alternatives.

v8bot: ryan_gahl has given a lamb chop to keepinitreal

keepinitreal now has 1 lamb chops

[Isaac Schlueter]

ryan_gahl, you are the winner. I happen to know that keepinitreal
loves lamb chops :)

It wasn't my intent to imply that everyone just ought to already know
about all these options. If anything, the multitude of options makes
them all less visible/relevant.

A single solid solution like python's VirtualEnv would be great, and I
think it'll come some time after node-0.5. We're all just busy doing
other things at the moment.

--i

[tjholowaychuk]

I will probably work on this stuff tonight

[Qing Guan]

Because the development of node is so rapid, I suspect that in the near future, the real problme we will facting is not

 

just how to manage multi version of nodejs, but also how to manage multi nodejs

 

ecosystem(nodejs+npm+modules+applications), even that ecosystem is based on the same vesion of node.

   This is a typical problem for node application developer.

A single solid solution like python's VirtualEnv would be great, and I
think it'll come some time after node-0.5.  We're all just busy doing
other things at the moment.

--i

My project, neco, is pretty close to this goal. It should be released the first stable vesion, 0.0.5, soon after the node 0.4.

[aaronblohowiak]

I created a minimal application that demonstrates the endless redirect
loop here: https://github.com/aaronblohowiak/connect-auth-37-bug-example

I have updated the wiki.

On Feb 2, 12:23 am, Ryan Dahl <r...@tinyclouds.org> wrote:
> On Tue, Feb 1, 2011 at 10:26 PM, aaronblohowiak
>

[Mikeal Rogers]

First go at support for 0.3.6 in request.

https://github.com/mikeal/request/commit/cb403a4cfdbe3d98feb9151fdbdae1e1436e59ab

request() now returns an object, Request, that can be treated as a stream. untested, and requires my pending patch to core for the pipe event.

[Laurie Harper]

On 2011-02-02, at 2:41 PM, Isaac Schlueter wrote:
> Managing multiple versions of node is an extremely oversolved problem.

So it seems :)

Thanks everyone for the suggestions, I'll pick one and try it, safe in the knowledge that if I don't like it I have lots of other options ;-)

L.

[Liam]

Is there going to be a beta period for 0.4?

Asking because it seems like the commit rate is pretty high still...

[Qing Guan]

---------- Forwarded message ----------
From: Liam <networ...@gmail.com>
Date: 4 February 2011 11:44
Subject: [nodejs] Re: Friendly Reminder: Move Code to v0.3
To: nodejs <nod...@googlegroups.com>


>>Is there going to be a beta period for 0.4?

>>Asking because it seems like the commit rate is pretty high still...

same question, 0.3.8 still on schedule ?

[Ciaran]

Vows is working ok for me on 0.3.8.

On Wednesday, February 2, 2011, aaronblohowiak

<aaron.b...@gmail.com> wrote:
> Is anyone successfully running connect-auth with Github-based OAuth on
> 0.3  branch?  I am running into an infinite redirect loop that i'd
> rather not debug if someone else has already fixed the issue. the same
> code runs fine on 0.2.5.

Aaron I got your bug report on connect-auth, I was waiting until tj
was happy with connect on 0.3.x before pushing on. There were
problems with node-oauth on 0.3.8, which I've looked at, I've not yet
fixed the oauth2 support in it yet, which might be the route issue :)

The good news is it will be a trivial issue to fix as soon as connect
is good to go
- cj

>
> Ta,
>
> Aaron
>
> On Jan 31, 6:55 pm, Ryan Dahl <r...@tinyclouds.org> wrote:
>> In the next week we will be releasing the next stable branch v0.4.
>>
>> v0.4, like v0.2, will offer JavaScript, C++, and binary interface stability.
>>
>> Please begin moving your code to v0.3.
>>
>> Update this Wiki page with any troubles:https://github.com/ry/node/wiki/Migrating-from-v0.2-to-v0.3
>

[Ryan Dahl]

On Thu, Feb 3, 2011 at 7:44 PM, Liam <networ...@gmail.com> wrote:
> Is there going to be a beta period for 0.4?
>
> Asking because it seems like the commit rate is pretty high still...

The beta period is now.

[Liam]

On Feb 4, 8:28 am, Ryan Dahl <r...@tinyclouds.org> wrote:

> On Thu, Feb 3, 2011 at 7:44 PM, Liam <networkimp...@gmail.com> wrote:
> > Is there going to be a beta period for 0.4?
>
> > Asking because it seems like the commit rate is pretty high still...
>
> The beta period is now.

Then perhaps release an 0.4b1? That might draw in more folks, esp
since 0.3 is advertised as "unstable".

[Mikeal Rogers]

This has been stated before, but probably not clearly enough.

Odd releases, like 0.3.x, *are* the alpha/beta period for a stable even release, 0.4.

I don't think ryan plans on adding any a,b,rc or other qualifiers to stable release numbers, if a release is stable, it's even, the unstable period for that release is the odd release cycle before that release.

[Liam]

Oh, I inferred that unstable meant APIs could shift, some changes are
experimental, new features are partially complete -- ie "alpha". If
0.3 has "reached stability" it might make sense to flag that
somehow...

[Koichi Kobayashi]

小林 (koichik) です．

ちょっと古いですが，本家 ML にて．

Date: Mon, 31 Jan 2011 19:01:38 -0800
From: Mikeal Rogers <mikeal...@gmail.com>
To: nod...@googlegroups.com
Subject: Re: [nodejs] Friendly Reminder: Move Code to v0.3

> The registry (http://search.npmjs.org/) shows that these libraries are highly depended on (more than 15 other modules depend on them):
>
> underscore
> connect
> request
> vows
> express
> joose
> coffee-script
> test
> colors
> jsdom

この辺がパッケージ作者に人気のパッケージと言えるようです．
underscore はともかく，joose も意外に使われてるんですね．

--
<component name="koichik">
<property name="fullName">"Koichi Kobayashi"</property>
<property name="email">"koi...@improvement.jp"</property>
<property name="blog">"http://d.hatena.ne.jp/koichik"</property>
<property name="twitter">"http://twitter.com/koichik"</property>
</component>

[Koichi Kobayashi]

it was wrong post, sorry folks.

Date: Sat, 05 Feb 2011 21:00:00 +0900
From: Koichi Kobayashi <koi...@improvement.jp>

[jbalonso]

On Jan 31, 9:55 pm, Ryan Dahl <r...@tinyclouds.org> wrote:
> In the next week we will be releasing the next stablebranchv0.4.

Awesome. I see the new release in the git tags, but I don't see a
"v0.4" or a "stable" branch yet... and I'd like to follow such a
branch. Will there be one?

Cheers,
Jason