4 ms·
Many high-profile open source projects have far more bug reports than they know what to do with. Declaring issue bankruptcy and asking people to re-test with a
by skybrian 12y ago
Many high-profile open source projects have far more bug reports than they know what to do with. Declaring issue bankruptcy and asking people to re-test with a new version is annoying from a customer service point of view, but looked at another way, it's a scalable way for the community to help. Cut and paste (or better yet, summarize the conversation) isn't so hard if it's still a real issue.
- frowaway001 12y agoOr ... TypeScript developers could just have added test cases to their test suite and figure out automatically whether the new implementation fixed things or caused regressions.
- hvs 12y ago"just adding test cases" is not a free act. It requires work on the developers part.
- frowaway001 12y agoSure. It's just the decision between " our bug reporters and all the time and work they spent" vs. "let's go through the issue database and migrate tickets which look useful. I mean, really? Less than 600 bugs, and they couldn't be bothered? Even with a small team. this could have been done in a day. And it's not like it would be extra work, because going through the bug tracker and trying to get a broader view of the issues raised should be a thing which happens continually anyway.
- thornkin 12y agoThat doesn't help if (as stated above) there are a lot of duplicate issues. You still have to figure out which test case applies to each report.