[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs project mission (was Re: "If you're still seeing problems, ple
Re: Emacs project mission (was Re: "If you're still seeing problems, please reopen." [
Fri, 29 Nov 2019 09:17:02 +0000
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix)
Richard Stallman <address@hidden> writes:
> > Whereas in most other projects both the repository and the bug tracker
> > the public and visible, and easy to observe that development work is
> > going on, recent reports are being handled, meaning they are welcome,
> > and whatever grievances the user has have the possibility to be fixed.
> This is an argument that users often would _like_ to look at the bug
> tracker. They don't _need_ it, but having it would motivate them.
FWIW, I was always under the impression that, before you even consider
writing a bug report, it is good manners to check, whether the issue
is already reported, or perhaps solved in the dev branch.
Searching "proper bug reporting", the first thing I get is:
How to write a good bug report: step-by-step instructions
1. Isolate bug. The first step in in writing a bug report is to
identify exactly what the problem is. ...
2. Check if you are using the latest version. Bug reports should be
based on the the latest development build . ...
3. Check if the bug is known. .
- Re: Emacs project mission (was Re: "If you're still seeing problems, please reopen." [,
Memnon Anon <=