search

nodejs / roadmap

This repository and working group has been retired.
135 stars 42 forks source link

About NG on ROADMAP.md #25

Closed bnb closed 2 years ago

bnb commented 9 years ago

The ROADMAP.md is extremely vague about what NG actually constitutes. Do you have very basic examples of a few things that would happen on the NG build? Also, how often would it be updated? With every push to NG core? Nightly? Following a version of SemVer?

mikeal commented 9 years ago

NG is vague because nothing has been decided yet, everything is somewhat up for debate.

The purpose of NG is to have a place where people can work on the "next generation" platform, potentially moving past some of the locked APIs in core today. How that will happen and what it will look like are still very much up for debate and I expect to see some awesome work there soon :)

bnb commented 9 years ago

Okay that sounds good. Would you be willing to say something to that effect in ROADMAP.md? I think that's a lot more committal without being actually committal. Essentially, that says to me that we know what we are doing, but just haven't laid everything out yet.

jonathanong commented 9 years ago

aside: any way to test this out, preferably using nvm?

bnoordhuis commented 9 years ago

Not yet. I maintain a next branch but no releases have been made yet (because there isn't much to release so far.)

Trott commented 2 years ago

Closing all issues in this archived repository.