Retiring the component would be a massive loss of data and alignment between projects. This before retirement proposal we should have a plan on how to manage this area properly. Granted, this is a messy area without clear ownership thus we can argue on what team / who should be the owner of the component.
In fact the component combines two different use cases (Examples and Demos) and it is not helping that different Qt projects have differently named components for the same overall use case. In Product Management we use quite a lot of these Demo components to track demos we need to create for specific customer verticals or events, marketing needs etc. Our master board is here: https://bugreports.qt.io/secure/RapidBoard.jspa?rapidView=83 If we touch this area I'd be welcoming on splitting the Examples and Demos in to two separate use cases but this is not an issue for just QTBUG project, this goes across the board and over several projects. Doing this will be quite a big one time effort but should improve the content accuracy. Regards, Stu -- Product Owner, Qt Platforms +358408031045 / santtu.aho...@qt.io -----Original Message----- From: Development <development-boun...@qt-project.org> On Behalf Of Paul Wicking Sent: maanantai 7. syyskuuta 2020 13.27 To: Qt development mailing list <development@qt-project.org>; Product Management <productmanagem...@qt.io> Cc: inter...@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.wick...@qt.io https://qt.io The Future is Written with Qt -- _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
