News for hackers. Stuff that matters.
Re:State of React Native 2018 by e40 on Friday June 15, 2018 @10:21AM (#17319952)
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?!?

Re:State of React Native 2018 by dgoldstein0 on Friday June 15, 2018 @10:32AM (#17320035)
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

Re:State of React Native 2018 by kbsletten on Friday June 15, 2018 @10:29AM (#17320013)
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.
Re:State of React Native 2018 by valuearb on Friday June 15, 2018 @04:54PM (#17323482)
Huh? You don't need a spidey sense to close a bug you just fixed, you just close it.
Re:State of React Native 2018 by HectorRamos on Friday June 15, 2018 @05:13PM (#17323610)
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.

Re:State of React Native 2018 by valuearb on Monday June 18, 2018 @04:11PM (#17341302)
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.
Re:State of React Native 2018 by _Tev on Tuesday June 19, 2018 @01:56PM (#17348862)
So they cannot do even the basic issue tracking? Wow, what a mess.