Version release #85

Closed
scunningham opened this Issue Feb 9, 2012 · 13 comments

2 participants

@scunningham

A query more than an issue: When is the next planned version release? v1.0 was back on May 11, 2011, and there have been a ton of changes since then.

@bnoordhuis
Node.js Foundation member

I suppose I could tag it v1.1 or v2.0 but what does it mean? There's been steady on-going development. I don't know of a key commit that would warrant a version bump. It'd be somewhat arbitrary.

@scunningham
@bnoordhuis
Node.js Foundation member

Fair point about the API changes. I'll tag v2.0 in a week or two, remind me if I forget.

For now, use 2498961 if you want a newer-but-stable commit to work with, it's what node.js ships with.

@scunningham
@bnoordhuis
Node.js Foundation member

Here's your reminder. Lots of activity on the project: clearing issues out for a tag?

Yes, kind of. There are two issues I want to lick (#97 and #99, provided that last one turns out to be a real bug) and then I'll put out v2.0.

@scunningham
@bnoordhuis
Node.js Foundation member

@scunningham: Sorry for the delay. I'm going to postpone this until node v0.8 is out. Lack of time, you know how it is.

@scunningham

Understood. Thanks for keeping me abreast.

@scunningham

Ben,

Quick ping on this. node v0.8 out a while. Any chance we can get that tag?

Thanks,
Sean

@bnoordhuis
Node.js Foundation member

The http_parser in v0.8 is the same as in v0.6 (commit da91852), it hasn't been upgraded since v0.6.16. I can tag the current HEAD and call it a day if you want. :-)

@scunningham
@bnoordhuis
Node.js Foundation member

Done. :-) 3fb4e06 is the commit and, unimaginatively, v2.0 is the tag.

@bnoordhuis bnoordhuis closed this Oct 10, 2012
@scunningham
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment