Hello, 2011/2/17 OpenSC <webmas...@opensc-project.org>: > If you claim this behavior is a regression, how does it look like with > OpenSC versions before 0.12.0? If you think that something is a > regression, it would be best if you demonstrated it and show the evidence > (output with a working version, output with a problematic version, logs > etc) instead of requiring developers to do it. Information in a good bug > report should be sufficient to be able to reproduce it '''if deemed > necessary''', not to '''require''' testing and comparing and debugging. I > added a note about it to ReportingBugs page as well. '''Please''' read it. > And [http://www.catb.org/esr/faqs/smart-questions.html#intro the links] on > that page as well.
It is difficult to do correct bug reports. Some people are slowly progressing. When reporting a bug to Apple the bug report template is not empty but already contains: "Summary: Steps to Reproduce: Expected Results: Actual Results: Regression: Notes: " A "description format" link links to an even more detailed template: "Summary: Provide a descriptive summary of the issue. Steps to Reproduce: In numbered format, detail the exact steps taken to produce the bug. Expected Results: Describe what you expected to happen when you executed the steps above. Actual Results: Explain what actually occurred when steps above were executed. Regression: Describe circumstances where the problem occurs or does not occur, such as software versions and/or hardware configurations. Notes: Provide additional information, such as references to related problems, workarounds and relevant attachments. " Is it possible to have templates in bug reports with trac? I could not find anything like that. But I am not a trac admin. I can use an URL like https://www.opensc-project.org/opensc/newticket?description=foobar but I don't know how to have a multi-line description. Bye -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
