Several developers on the mailing list have expressed a wish to return to the pre-launchpad system of having separate places for bug reports and feature requests.There is a group of people who check new reports and try to help where they can, but they are not organized as a team, and not all of them seem to have permission to change a bug's importance or to milestone it for a specific release.Launchpad provides a system to label feature requests as 'wishlist' items, and to add various kinds of tags to an issue. Feature requests and bug reports, as well as some usage errors and questions all end up in the same place, which in its current state is not welcoming to users nor to (possible new) developers, due to the sheer amount and the missing categorization. Bug reports are not currently systematically triaged, tagged, labelled or otherwise sorted.The registration process for a launchpad account (via Ubuntu One) can seem deterrent to a user. To report a bug, one needs to have an account on launchpad.Bryce has written up a possible, ideal scenario for a bug workflow for Inkscape. There is a web page that describes the process. There is no template, or a step-by-step instruction on launchpad for the minimum requirements of a good report. Users are usually not guided in making their bug reports/feature requests, resulting in many unclear bug reports, duplicate reports and insecurity of what to do for the users, probably also in some bugs going unreported.As of February 22, 2018, there are 4748 open and 1826 new bugs listed. After the Inkscape project's move to GitLab for the hosting of its source code repository (and various other repositories), the project's bug tracker is still on launchpad.
0 Comments
Leave a Reply. |