News for hackers. Stuff that matters.
Re:Closing 45% of the open Emacs bugs by tpmx on Saturday August 14, 2021 @12:44PM (#28182042)
146 messages in that bug thread. Wow.
Re:Closing 45% of the open Emacs bugs by irrational on Saturday August 14, 2021 @12:56PM (#28182146)
> I'm going to go ahead and guess that the problems discussed were fixed, and I'm closing this bug report.

If only there was a way to find out, instead of guessing.

I’m going to start trying this at work. I wonder how it will be received?

Re:Closing 45% of the open Emacs bugs by namdnay on Saturday August 14, 2021 @01:06PM (#28182221)
> I’m going to start trying this at work. I wonder how it will be received?

You’ve never done that at work? In every company I’ve worked for, nobody would bat an eyelid at dropping an issue that hasn’t been touched for more than a year

Re:Closing 45% of the open Emacs bugs by nsizx on Saturday August 14, 2021 @01:28PM (#28182405)
That's how we got that stupid bot on GitHub that constantly says "comment here or I'll close this". From time to time I have to waste my time that way. I wonder if this means maintainers want us all day bumping bugs?
Re:Closing 45% of the open Emacs bugs by arthur2e5 on Saturday August 14, 2021 @01:56PM (#28182665)
I have this “ready with tests” PR for almost a year now, and every time I get a notification it’s either the bot or someone who really wants the PR to be merged bumping it up for me. I don’t even care so much about it any more…
Re:Closing 45% of the open Emacs bugs by irrational on Saturday August 14, 2021 @02:38PM (#28182960)
Without testing to see if it is actually fixed? Never. Though, to be honest, it is QA who is testing it, not us developers. But, only QA can close a ticket and no way would they close it without being 100% sure it is fixed.
Re:Closing 45% of the open Emacs bugs by kortilla on Saturday August 14, 2021 @05:18PM (#28184025)
> Though, to be honest, it is QA who is testing it, not us developers.

Developers absolutely should be testing for the issues they know about. QA is there to look for unknown issues.

Any company that depends on QA for testing and doesn’t make devs to it is miserable to work for (both as a dev and a QA).

Re:Closing 45% of the open Emacs bugs by irrational on Saturday August 14, 2021 @05:31PM (#28184108)
Not where I work. QA are the ones who first look at all reported issues. They see if they can replicate the reported issue. If they can’t they contact the reporter and try to figure out why they can’t replicate it. Once they can replicate it they write up the ticket with replication steps and add it to the backlog to be assigned out in a sprint. They attend all meetings and explain the issues. Once the developer thinks they have fixed the issue they send it back to QA to verify it is fixed. Then QA reaches out to the person that reported the issue to tell the about the resolution.
Re:Closing 45% of the open Emacs bugs by kortilla on Tuesday August 17, 2021 @12:04AM (#28206120)
That’s not testing, that’s triage. If you don’t bother writing unit tests yourself as a developer when you fix the tickets, then that’s the problem I’m referring to.
Re:Closing 45% of the open Emacs bugs by cdcarter on Saturday August 14, 2021 @11:30PM (#28186045)
Have you ever sent the issue back to QA as fixed, and then they do their reproducer and it’s not fixed? That’s roughly the scenario we’re asking you to have empathy toward.
Re:Closing 45% of the open Emacs bugs by phkahler on Saturday August 14, 2021 @02:52PM (#28183052)
For QA to test tell if it's fixed, they must have a test case. If there is a test case here, the devs wouldn't have to guess?
Re:Closing 45% of the open Emacs bugs by joshuaissac on Saturday August 14, 2021 @02:59PM (#28183095)
The bug reproduction steps (along with expected vs actual behaviour) are in the opening comment of the bug report, so they really should not have had to guess.
Re:Closing 45% of the open Emacs bugs by irrational on Saturday August 14, 2021 @05:32PM (#28184112)
See my response to kortilla above.
Re:Closing 45% of the open Emacs bugs by Chilinot on Saturday August 14, 2021 @03:13PM (#28183197)
QA is not your test suite. Test your own code, submit working code, let QA try to break it.

Dont just push code and expect others to point out your flaws. Take some responsibility.

Re:Closing 45% of the open Emacs bugs by irrational on Saturday August 14, 2021 @05:32PM (#28184115)
See my response to kortilla above.
Re:Closing 45% of the open Emacs bugs by dragonwriter on Saturday August 14, 2021 @04:40PM (#28183764)
In most places I’ve worked, having a bug untouched for even a fairly small fraction of that time would result in someone getting, at a minimum, corrective counseling.
Re:Closing 45% of the open Emacs bugs by kortilla on Saturday August 14, 2021 @04:53PM (#28183848)
Corrective counseling for a single bug? I take it you’ve never worked in a US software company.
Re:Closing 45% of the open Emacs bugs by taeric on Saturday August 14, 2021 @01:08PM (#28182239)
Yeah... This actually seems standard for old backlogs.

Were all problems fixed? Almost certainly not. Many will have become overcome by events, though. The ones that are still pertinent will reopen.

Such that anytime I see a large percentage of bugs closed like this, this reflects more on working in the ticketing system than it does on fixing the problem it is managing.

Re:Closing 45% of the open Emacs bugs by jerrysievert on Saturday August 14, 2021 @12:58PM (#28182160)
I’m going to guess that when you close issues that are years old, a fraction of them will reappear as enough people have devised workarounds for the issues and they will become the de facto fix.
Re:Closing 45% of the open Emacs bugs by thrower123 on Saturday August 14, 2021 @03:13PM (#28183195)
Everybody does this, it's the normal behavior with enterprise bugs.

They report something. You badger them for six weeks to collect enough information to reproduce it. You fix the problem and slate it into a release and make it available. They don't take the release for another seven months.

Re:Closing 45% of the open Emacs bugs by aprdm on Saturday August 14, 2021 @01:40PM (#28182513)
I’ve done this at work many times, it’s the only way I’ve found to keep a big project back log under control… if people care enough they can reopen
Re:Closing 45% of the open Emacs bugs by toast0 on Saturday August 14, 2021 @01:21PM (#28182354)
When I worked for Facebook, the had a bugtracker bot that closes open issues after 6? months of no activity. It's sort of nice, but also terrible.