diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 54a258533..a9a67a1c7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -24,24 +24,24 @@ quickly merge or address your contributions. ### Reporting an Issue -* Make sure you test against the latest released version. It is possible - we already fixed the bug you're experiencing. Even better is if you can test - against `master`, as bugs are fixed regularly but new versions are only - released every few months. +* Make sure you test against the latest released version. It is possible we + already fixed the bug you're experiencing. Even better is if you can test + against the `main` branch, as the bugs are regularly fixed but new versions + are only released every few months. * Provide steps to reproduce the issue, and if possible include the expected results as well as the actual results. Please provide text, not screen shots! * If you are seeing an internal Vault error (a status code of 5xx), please be sure to post relevant parts of (or the entire) Vault log, as often these - errors are logged on the server but not reported to the user + errors are logged on the server but not reported to the user. * If you experienced a panic, please create a [gist](https://gist.github.com) of the *entire* generated crash log for us to look at. Double check no sensitive items were in the log. * Respond as promptly as possible to any questions made by the Vault - team to your issue. Stale issues will be closed periodically. + team to your issue. ### Issue Lifecycle @@ -58,9 +58,14 @@ quickly merge or address your contributions. referenced in the commit message so that the code that fixes it is clearly linked. -5. The issue is closed. Sometimes, valid issues will be closed to keep - the issue tracker clean. The issue is still indexed and available for - future viewers, or can be re-opened if necessary. +5. The issue is closed. + +6. Issues that are not reproducible and/or not gotten responses for a long time are + stale issues. In order to provide faster responses and better engagement with + the community, we strive to keep the issue tracker clean and the issue count + low. In this regard, our current policy is to close stale issues after 30 days. + Closed issues will still be indexed and available for future viewers. If users + feel that the issue is still relevant, we encourage reopening them. ## Pull requests