Hi nabog,
Re: github vs. codeplex - totally agreed! We'll consider it once we ship 1.0. But for now, we're a small team, and we need to prioritize :-). Moving to github means we have to find suitable replacements for or build new processes around:
Re: slow responses. Nostra culpa, nos paenitet - our fault, we're sorry - thanks for calling us out on that :-). We hope to get back into our groove soon, but for now we're a bit spread thin as we work on testing and stabilizing the 1.0 release, figuring out a plan for the next release (we recently conducted a survey here), working with internal folks interested in Node.js/npm, as well as promoting NTVS in some presentations/demos. Once again, though, thanks for voicing your concern - we'll try to amp up the communication.
Re: VS2015 - we've been focusing on providing a stable 1.0 release (which will not support VS 2015), so VS 2015 bugs have been deprioritized for the time being. That said, that's no excuse for not putting up a recent dev build, so we'll try to put one up by the end of the week - just know that many of these the VS 2015 specific issues haven't been fixed yet. In the meantime, feel free to dive into the source code - we <3 pull requests
Anyways, seriously - thanks again for the helpful feedback - we really appreciate it.
Re: github vs. codeplex - totally agreed! We'll consider it once we ship 1.0. But for now, we're a small team, and we need to prioritize :-). Moving to github means we have to find suitable replacements for or build new processes around:
- discussions
- issue tracking
- documentation
- releases
-
reviews
Re: slow responses. Nostra culpa, nos paenitet - our fault, we're sorry - thanks for calling us out on that :-). We hope to get back into our groove soon, but for now we're a bit spread thin as we work on testing and stabilizing the 1.0 release, figuring out a plan for the next release (we recently conducted a survey here), working with internal folks interested in Node.js/npm, as well as promoting NTVS in some presentations/demos. Once again, though, thanks for voicing your concern - we'll try to amp up the communication.
Re: VS2015 - we've been focusing on providing a stable 1.0 release (which will not support VS 2015), so VS 2015 bugs have been deprioritized for the time being. That said, that's no excuse for not putting up a recent dev build, so we'll try to put one up by the end of the week - just know that many of these the VS 2015 specific issues haven't been fixed yet. In the meantime, feel free to dive into the source code - we <3 pull requests
Anyways, seriously - thanks again for the helpful feedback - we really appreciate it.