On Thu, Jul 03, 2014 at 08:41:37PM +0100, Richard Moore wrote: > 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. > i think some people in the project are a bit too dogmatic in this regard. good test cases are typically so short and "unimaginative" that they cannot reasonably violate copyright or patents, and can therefore be safely submitted to gerrit by anyone. if you deem a test case to be complex enough to be considered a creative work or invention (which would usually be a bad sign to start with), you can still point the reporter to the contribution process.
> - Please make clear that security issues should be reported to > [email protected] > i added that. i also clarified the clause directed at commercial customers. > Cheers > > Rich. > > > > On 3 July 2014 15:31, Friedemann Kleint <[email protected]> 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 > > [email protected] > > http://lists.qt-project.org/mailman/listinfo/development > > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
