[Development] Guidelines for reporting bugs in Qt

[Richard Moore]

Overall this is very good, but there are a couple of things that could be
improved:

- Asking people for a unit test in the bug tracker when we're not allowed
to include this in Qt without submission via gerrit seems likely to cause
conflict. I'd suggest either removing this section or explaining a
mechanism that would allow the test to be used.

- Please make clear that security issues should be reported to
security at qt-project.org

Cheers

Rich.



On 3 July 2014 15:31, Friedemann Kleint <Friedemann.Kleint at digia.com> wrote:

> Hi,
>
> as a result of internal discussions at Digia, I have updated
> http://qt-project.org/wiki/ReportingBugsInQt a bit. The motivation
> behind this is that we want the bug reports as good as possible since
> many roles in the Qt project deal with them (developers, code reviewers,
> release managers, people trying to check for regressions, ...) and thus
> it is important that bug reports are easy to understand and to reproduce.
>
> I would like to have more opinions on the guidelines at
> http://qt-project.org/wiki/ReportingBugsInQt . Is there anything missing
> that would make fixing bugs easier in the modules you maintain?
>
> Once we have the guidelines in a good shape, they will be shown
> prominently on the JIRA-landing page.
>
> Regards,
> Friedemann
>
> --
> Friedemann Kleint
> Digia, Qt
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20140703/8cbe2fd5/attachment.html>