When reporting issues, it can be time-consuming or challenging to determine whether the issue has already been reported. This could include cases where the issue has already been closed as fixed or exists in an upstream repository.
People often lack the time to closely follow the development of all packages. Therefore, having a quick way to check whether an issue is already being worked on or has been fixed but not yet released could be helpful. If used properly, it could reduce the number of duplicate issues and save time when debugging / creating reproductions for things that have already been fixed.
There could also be a board of "known issues" in a new version of a package.
That's why I would like to propose a version of unsight for users, not maintainers. This would allow them to easily find issue clusters - both open and closed - that are similar to their problem.
When reporting issues, it can be time-consuming or challenging to determine whether the issue has already been reported. This could include cases where the issue has already been closed as fixed or exists in an upstream repository.
People often lack the time to closely follow the development of all packages. Therefore, having a quick way to check whether an issue is already being worked on or has been fixed but not yet released could be helpful. If used properly, it could reduce the number of duplicate issues and save time when debugging / creating reproductions for things that have already been fixed.
There could also be a board of "known issues" in a new version of a package.
That's why I would like to propose a version of unsight for users, not maintainers. This would allow them to easily find issue clusters - both open and closed - that are similar to their problem.