Please discuss feature requests in community forums #5541
Labels
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
{{ message }}
On Signal Desktop we rely on high-quality bug reports in order to triage, prioritize, diagnose, and fix the problems that users discover. We're excited about the enhancements that have been added to Signal recently and we want that momentum to continue.
However, the sheer volume of legacy issues, combined with submissions that do not follow the provided issue template, have created a situation where there are currently lots of stale open tickets. Most of these issues have been inactive for several years and they reference versions of Signal that are no longer available. Many open issues are essentially ad-hoc discussion threads or feature requests that are a better fit for the community forum.
Our aim is to get to a point where we can effectively track actionable issues in the GitHub repository. Community involvement plays a large role in our development and planning process, and we closely follow the forums and other feedback channels. Through these channels we collect the feedback and suggestions for feature requests, many of which we are working on every day.
We have already taken some steps to turn this repository into a functional issue tracker for bug reports:
Users are welcome to re-submit bug reports that follow the updated issue template and that still affect the current release of Signal. By re-submitting valid issues with up-to-date reproduction steps (and debug logs that were produced by a recent version of Signal) the developers will be better equipped to solve any underlying problems. Please include the legacy issue ID in your new submission if there is important context available in the old thread.
We need the community to help us with this step, and we sincerely appreciate your participation in this cleanup effort.
The text was updated successfully, but these errors were encountered: