7 ms·

but we never close them when they are fixed, causing them to pile up This is the problem. Why not close them when they are fixed?!?

• kbsletten 8y ago
  Well, unless they have a triage team, you're counting on developers having a Spidey-sense that there's an open issue related to what they're working on. I assume the issue list is something they never asked for but feel obligated to doing a minimal amount to clean up.
  • valuearb 8y ago
    Huh? You don't need a spidey sense to close a bug you just fixed, you just close it.
    • HectorRamos 8y ago
      This assumes that the person fixing the bug is either the same one who filed the bug, or they were motivated to fix the bug after finding the GitHub issue. In many cases, the fix comes from within Facebook or from a different contributor when we/they run into the issue themselves.
      • valuearb 8y ago
        And this is exactly why React Native is such an unprofessional pile of crap. Random code changes from random people with no prioritization, documentation or coherent history.
      • _Tev 8y ago
        So they cannot do even the basic issue tracking? Wow, what a mess.
• dgoldstein0 8y ago
  If you have enough issues, just deduping and knowing when a commit fixes an issue to remember to close it becomes a problem. Not saying this is an excuse, but it's unfortunate reality that "close most issues, see which ones come back" is one of the easier ways to focus on the most important bugs