npm in 0.10 LTS about lts HOT 13 CLOSED

@nodejs/lts @rvagg ... need to make sure this is on the agenda for the next LTS WG call.
@nodejs/tsc ... fyi

from lts.

We only had three on the call today so we're going to defer this discussion to the next LTS call.

from lts.

After discussing it on the LTS WG call today, the current plan is to include a clear warning in the upcoming v0.10.41 release that npm will be updated to the latest npm@2 version in v0.10.42. Additionally, a blog post on nodejs.org would communicate the plan to update npm in v0.10.42, detail the breaking changes and rationale for the update, and give users plenty of notice that the update is coming (and give them time to push back should anything truly critical break).

The actual npm update would not land until v0.10.42.

@nodejs/tsc and @nodejs/LTS WG members... we need your input on this plan.

from lts.

include a clear warning in the upcoming v0.10.41 release

what is the nature of this proposed warning? will npm be spitting out a console message about it or just a changelog notice?

from lts.

I believe that's still to be determined. @zkat @othiym23 ?

from lts.

I can go ahead an put together an [email protected] this week that will barf on attempts to install scoped packages and print a message with whatever text the WG wants indicating that 0.10.42 will be including npm@2. I could, among other things, link to this issue. ;)

from lts.

Instead of giving a version number, it'd be better to provide a date. If any security issue comes up that forces us to release 0.10.42, we'd have to make the breaking change sooner than expected (or postpone to 0.10.43 and create a lot of confusion).

Conversely, nobody has any idea when 0.10.42 might be released, and if it'll ever happen at all, so it also doesn't create a great sense of urgency.

from lts.

@piscisaureus I believe that the abovementioned issue fixed by npm/npm@b9474a8 is worth a release in 0.10 branch, the earlier the better.

Note that is has been already two months since that fix.

from lts.

A candidate for the transitional [email protected] release is available as npm/npm#10152. Feel free to comment on the messaging of the deprecation banner, but be aware that my preference is that it be somewhat long and ugly – the whole goal of this is to encourage everyone to transition away from npm@1 as expeditiously as possible. I'd like to land this in the first 0.10 LTS release, so it would be good to know where and how I should submit the PR to get this reviewed and incorporated into the 0.10 LTS release-candidate branch.

Please note that this release includes no security fixes, and is intended as a transitional release on the path to landing npm@2 in 0.10 LTS. The npm@2 version submitted for 0.10 LTS will contain all of the extant security patches available as of the time that it's downstreamed to the LTS branch.

from lts.

[email protected] is now a thing (those release notes are worth reviewing carefully). @chrisdickinson tells me that https://github.com/nodejs/node/tree/v0.10 is the base against which I should land the PR including it in the tree, but I'll hold off on assembling that PR until somebody (preferably @rvagg or @jasnell) tells me that's the proper place to do it.

from lts.

@othiym23 ... Yes, but I'm considering creating v0.10.x-staging and v0.12.x-staging branches to parallel v4.x-staging. We'll put this on the LTS WG meeting agenda for monday.

from lts.

@othiym23 ... based on the LTS WG discussion today, I've created the v0.10-staging and v0.12-staging branches. Please open a PR for the npm update against the v0.10-staging branch.

from lts.

Related: nodejs/node#5570

from lts.