Week of 7/27 at npm

So I missed posting this here last week here, but it was up on our roadmap.

My weeks are looking pretty much the same while we burn through the open 3.x bugs. Once the queue is worked through we’ll be ready to move it out of beta!

This week I’m…

  1. Triaging v3.x issues for next weeks release
  2. Completing this weeks issues. (This has gotten its way up to 9 items, so I may be reconsidering some of them. =D
  3. File an issue on npm/issue-tracker to discuss how npm ls should work
  4. Make an issue to track discussion of how deprecation warnings are handled

Last week I…

  • Triaged the weeks v3.x issues into the up coming release buckets.
  • Finished off the v3.2.0 issues. See the tactical roadmap below for details.

And the week before I…

  1. Worked on the v3.1.3 issues (as of this writing): #8891 npm rm -g misbehaving if was a symlink, #8874 linking scoped modules fails, #8812 improve progress bar, #8701 improve permission validation on windows
  2. Triaged v3.x issues for next week (tentatively v3.1.4).

Week of 7/13 at npm

This week I’m…

  1. Working on the v3.1.3 issues (as of this writing): #8891 npm rm -g misbehaving if was a symlink, #8874 linking scoped modules fails, #8812 improve progress bar, #8701 improve permission validation on windows
  2. Triaging v3.x issues for next week (tentatively v3.1.4).
  3. Release and other issue support.

Last week I…

  1. Triage npm@3 bugs + features for this week
  2. DO them and release 3.2.03.1.1
  3. Continue working the npm@3 issues

And early this week I also released 3.1.2 as the 3.1.1 release was critically broken. This was a process issue (last minute inclusions in the release, late night release) which led to errors (tests run against wrong tree) which resulted in pushing out something that couldn’t install local modules. Pretty basic! We’ve altered our processes to say that if something isn’t done by EOD Wednesday then it’s not going in Thursday’s release.

My week of 7/6 at npm

This week is a slightly short week, as I’m taking Friday off so that me and mine can visit Acadia National Park one last time before moving away from the region. This week I’m…

  1. Triage npm@3 bugs + features for this week
  2. DO them and release 3.2.0
  3. Continue working the npm@3 issues

Last week I…

  1. Fixing bugs in the 3.0.13.1.0 milestone
  2. npm@3.0.13.1.0 release

It was a 3.1.0 release because of features ported forward from 2.x

My week of 6/29 at npm

This week is a short week for me– I’m only officially working two days, but I’ll still be doing a npm@3 release this Thursday.

  1. Fixing bugs in the 3.0.1 milestone
  2. npm@3.0.1 release

Last week I released the first beta of:

npm 3!!

Try it out today:

Or try out what’s guaranteed to be the beeldingedgiest, until such time as it’s out of beta:

My week of 6/22 at npm

This week I’m…

  1. 🌟 🌟Preparing to release a public beta of npm@3 🌟 🌟
  2. Nope, that’s probably it.

Last week… omg, so much got done. So as planned…

  1. Fixing the LAST THREE remaining failing tests in npm@3’s test suite!! #7774 This has been the albatross around my neck since late March!
  2. Attending CCSConf in New York this Thursday & Friday. Plus BrooklynJS this Thursday!
  3. #8138 Fix the stack-overflow that shows up with freshly minted ember apps and npm@3. With this, all known npm@3 issues will be resolved!

Then, in addition, I:

  1. Fixed all of the other remaining outstanding npm@3 blockers.
  2. Reran the test suite and found 23 more failing tests!
  3. #8587 Fixed all of those tests / bugs uncovered by those tests.
  4. Started writing the changelog for npm@3… it’s a tome.

My week of 6/15 at npm

Hey you all, so THIS week at npm, I’m.

  1. Fixing the LAST THREE remaining failing tests in npm@3’s test suite!! #7774 This has been the albatross around my neck since late March!
  2. Attending CCSConf in New York this Thursday & Friday. Plus BrooklynJS this Thursday!
  3. #8138 Fix the stack-overflow that shows up with freshly minted ember apps and npm@3. With this, all known npm@3 issues will be resolved!

As always, you can find out what the rest of my team at npm is doing at the roadmap.

Last week (and the week before) I…

  1. Released npm@2.13.3 while the rest of the team was away at NodeConf Adventure.
  2. Fixed a bunch of failing tests in my albatross #7774.
  3. Ended up adding substantially more ability to rollback already completed steps to npm@3 than was previously planned. This also resulted in infrastructure for making all of the changes we make to your node_modules undoable, which will ultimately make it much harder to get your node_modules into a broken state.

My week of 6/1 at npm

This week:

  1. #7774 Getting tests passing for multi-stage and npm@3. I found a nasty bug pre-conference so I’m gonna be landing a fix for that early this week. You’ll also find that the multi-stage branch now sports npm@3 style flat, deduped deps!

Last week, I conferenced at @jsconf all week. It pretty great. Lots of lovely people and fascinating conversations. Looking forward to talking to more of you all at future conferences.

My week of 5/26 at npm

This week, I’m at @jsconf all week. I may or may not get anything else done, but I’m not investing in a checklist this week.

Last week, I:

  • Did npm’s release, which thank’s to @othiym23‘s excellent documentation went almost flawlessly.
  • Fix a bunch more tests in #7774 (the npm@3/multi-stage branch test fixing ticket). I also found an error in rolling back optional dependency failures in dependency configurations. (Eg, deps that are both optional to one dep and non-optional to another, especially when more layers of indirection are involved.)

My week of 5/18 at npm

This week…

  1. #7774 npm@3 tests, I really want to get a lot of them done.
  2. If things go as planned, I’ll also be doing the release this week.

Last week I…

  • #8055 #8052 Documented a new module, a git repo manager which will be used in resolving these tickets. It’s shelved for the time being while I push on getting npm@3 out the door.
  • #7774 Got about a third of the tests passing
  • Interviewed four candidates for a position as a coworker on the CLI team. Everyone was amazing, and if we had the resources we’d hire them all. We’re doing additional interviews with the wider npm team this week, but eeee, we’re close to having more folks on our team!
  • I talked at the Boston Ember.js meetup (pics, video) about what’s new in npm@3. This was a repeat from a talk I gave earlier at a local Node.js meetup, but with a few updates.

My week of 5/11 at npm

I’m going back to finishing tests in the multi-stage branch, but I have one carry-over I want to get done. As always, this’ll be updated as we go over on the npm roadmap.

  1. #7774 Getting tests passing for multi-stage and npm@3
  2. #8055 #8052 Isolating git support in npm and making update and outdated checking work well– I started this last week and will be making a separate github repo for it shortly. It will likely be shelved after Monday, while I work on tests in multi-stage.
  3. Pluuus we’re going to start interviewing CLI candidates…

Last week I…

  • Got married!

  • Started work on #8055 #8052 Isolating git support in npm and making update and outdated checking work well

Whatever fills my mind…