Skip to content
This repository

June 2012 iteration planning #513

Closed
SteveSanderson opened this Issue · 7 comments

2 participants

Steven Sanderson Michael Best
Steven Sanderson
Owner

This is a place for us to discuss what we're aiming to do this month.

For myself, I propose:

  • Merge or close #326, #154, #226, #427, #282, #510, #512
  • Get agreement on which of the engineering debt issues (#495) we're going to tackle in the immediate future

Michael, would you be able to do a pass through any of the recently-filed issues and see which ones we can close immediately?

Michael Best
Collaborator
mbest commented

I'd like to set higher targets for the number of issues we deal with, something like 12 to 15 per month. I'm not counting issues that can be closed right away. So that's 12 to 15 issues that are dealt with through discussion, coding, reviewing, and merging.

To start, I'd like to have some discussion on #483 and #484. I added more details on the why and how for both of those and hope that we can discuss it like that before you have to look at any code.

I'll look through the list and pick another three that I think we can work on this month.

I think a good engineering debt to address is using JsHint. In general, I'm happy with the styles used in Knockout, although some are different from the styles I use in my work projects (skipping curly braces, for example).

Michael Best
Collaborator
mbest commented

Here are three issues that I think we can get to this month (all minor impact): #397, #205, #119.

I can go through the recent issues in the next couple days. I'll update here when I'm done.

Steven Sanderson
Owner

OK, thanks for the suggestions. I'll consider myself committed to doing the ones I listed in the original post, and will look at the others you've mentioned if capacity permits. In particular, the minor impact ones should be easy to resolve quickly.

Michael Best
Collaborator
mbest commented

I closed 11 of the recent issues and labeled them with 'not-a-bug', 'declined', or 'duplicate'. I also added 4 new issues for version 2.2 and marked those also with 'steve-to-review'.

Any issues that are still labeled 'Needs Review' are ones that I didn't feel I could make a decision on or that simply didn't seem urgent to decide right away.

Steven Sanderson
Owner

Update to help with tracking:

Michael Best
Collaborator
mbest commented

Great progress.

Michael Best
Collaborator
mbest commented

Thanks for taking care of #397, #205, #119; I've merged your implementations for each and closed them.

Michael Best mbest closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.