[Development] "Examples and demos" component in Jira (QTBUG project)

[Topi Reiniö]

+1. Going through the open bugs under 'Examples and Demos', it was clear that out of 149 items, only two fell clearly within the realm of documentation or documentation infrastructure, and all were better off with a specific module or area as a component. There's also the risk of critical issues not receiving immediate attention if they are discovered via an example and only reported against that component. We're better off without it.

\topi
________________________________
From: Development <development-bounces at qt-project.org> on behalf of Paul Wicking <Paul.Wicking at qt.io>
Sent: Monday, September 7, 2020 12:27 PM
To: Qt development mailing list <development at qt-project.org>; Product Management <ProductManagement at qt.io>
Cc: interest at qt-project.org <interest at qt-project.org>
Subject: [Development] "Examples and demos" component in Jira (QTBUG project)

Hi all,

Documentation engineers are most often not the right assignee for example bugs, which end up going stale. I propose to retire the "Examples and demos” component.

Bugs in examples are often discovered during package testing, or soon after release of a new minor version. In most cases, documentation engineers are the wrong assignees for these issues. The QTBUG project requires that all components have a default assignee, and Jira chooses the default assignee for an issue from its components in alphabetical order. Thus, most issues reported against the “Examples and demos” component end up with the Qt Documentation Team as the assignee, even if the reporter or triage team adds the component the code belongs to. The result is that these issues often receive almost as little attention as if they had been without an assignee in the first place. They go stale.

I have discussed this problem with the documentation engineers and some of the R&D area leads in TQtC. We believe the component mostly provides meta-information. That can be achieved by other means that do not require a default assignee. Therefore, we think it’s best to retire the component. The Documentation Infrastructure team will triage all "examples and demos” bugs during this week, with the goal of assigning the correct components and/or teams/maintainers to these tasks. When all tasks are triaged, the component will be retired. This means it will not be available when creating a new issue, and it will not impact our archives.

--
Paul Wicking
R&D Manager

The Qt Company
Sandakerveien 116
0484, Oslo, Norway
paul.wicking at qt.io
https://qt.io

The Future is Written with Qt
--

_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200909/f849e64e/attachment-0001.html>