https://bugs.documentfoundation.org/show_bug.cgi?id=150372
Philippe Cloutier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=42 | |673 --- Comment #35 from Philippe Cloutier <[email protected]> --- (In reply to Buovjaga from comment #34) > (In reply to Philippe Cloutier from comment #33) > > (In reply to Buovjaga from comment #32) > > > (In reply to Philippe Cloutier from comment #31) > > > > (In reply to Buovjaga from comment #30) > > > > > In any case, this report does not vanish > > > > > when closed, duplicates can and should be re-tested after a fix, if > > > > > there is > > > > > suspicion of remaining issues. > > > > > > > > It is unclear what you mean by "this report does not vanish when > > > > closed", > > > > but duplicates cannot be "re-tested", no. > > > > > > What is unclear about it? > > > > It is unclear what you mean by "closing a report". > > Changing the status to resolved or closed. It's unclear how a report could be closed, but there is no such status. > > > Why do you claim duplicates could not be re-tested, it doesn't make any > > > sense to me? > > > > A duplicate is just a ticket; it cannot be tested (or re-tested). One could > > re-test whether the issue persists, but what you're suggesting would be a > > waste of time. We don't mark tickets as duplicates just because we speculate > > solving one issue would also solve the other. > > I don't know what you mean by "we", but are you advocating for only closing > reports as duplicates when the issue has been fixed? Of course not. Basically, all I am saying is: A. We (software developers) do not mark issues as resolved until we have good reason to believe that they are. B. Duplicates must have overlapping descriptions. For example, if we have 3 tickets: 1. Fails to install on macOS 2. Fails to install on GNU/Linux 3. Fails to install …then #1 is not a duplicate of #2 and #2 is not a duplicate of #1. They *may* both be duplicates of #3, though, if the component of #3 includes the components of the others and the platform of #3 includes the platforms of the others. And #2 can *become* a duplicate of #1 if #1 is widened to encompass more than macOS. (This comment and any other from myself on this ticket is offered under the terms of CC0 1.0.) -- You are receiving this mail because: You are the assignee for the bug.
