Repository navigation
Replies: 4 comments
|
I’d dearly love to resolve/close #553! And if some of the issues are now fixed, let's get them closed. So maybe we start with the first 2 categories? |
|
Here is the first pass over the 38 issues opened before August, limited to the two categories you picked: claims I could test against Already done, or overtaken — suggest closing
Testable claims, reproduced on
|
|
Three of the bugs from that list are now fixed and closed: #746, #584, #634. The eleven I suggested closing are still open (#612, #526, #640, #494, #797, #4, #14, #279, #530, #831, #565), and I don't want to comment on any of them without your say-so. If going through all eleven is more than you want right now, name two or three and I'll start there. |
Uh oh!
There was an error while loading. Please reload this page.
There are 44 open issues and 11 PRs. Over half the issues are 3+ years old, and 11 of those have no comments at all — opened, never discussed, never closed. Eleven were filed in December 2022 alone.
If it's useful, I'd like to do the legwork on that so the decisions are cheap for you:
npm create indiekitin an empty directory reaches the wizard with no priornpm install, so the step it proposes isn't needed where it's placed. Two minutes to settle, four years open.I'd produce a list with evidence, not close anything myself — what stays open is your call. Happy to start with the December 2022 batch rather than all 44.
Not urgent, and it doesn't block v1.0 — the milestone is only 9 items.
All reactions