diff options
Diffstat (limited to '.github')
| -rw-r--r-- | .github/ISSUE_TEMPLATE | 35 | ||||
| -rw-r--r-- | .github/PULL_REQUEST_TEMPLATE | 33 | ||||
| -rw-r--r-- | .github/RELEASE_TRACKER_TEMPLATE | 12 | ||||
| -rw-r--r-- | .github/stale.yml | 25 |
4 files changed, 63 insertions, 42 deletions
diff --git a/.github/ISSUE_TEMPLATE b/.github/ISSUE_TEMPLATE index 306b4eebc15..386ed2d8dd5 100644 --- a/.github/ISSUE_TEMPLATE +++ b/.github/ISSUE_TEMPLATE @@ -1,13 +1,30 @@ -This repository (glusterfs) uses github issues to track feature requests *only*. +<!-- Please use this template while reporting an issue, providing as much information as possible. Failure to do so may result in a delayed response. Thank you! --> -For assistance with bugs, please file a bug in our bugzilla instance [1] +**Description of problem:** -For other queries regarding glusterfs, please post to the users [2] or devel [3] lists as appropriate. -You may further want to subscribe to these lists or view the archives for these lists, see [4] [5]. +**The exact command to reproduce the issue**: + + +**The full output of the command that failed**: +<details> + + + +</details> + +**Expected results:** + + +**Additional info:** + + +**- The output of the `gluster volume info` command**: +<details> + + + +</details> + +**- The operating system / glusterfs version**: -[1] glusterfs Bugzilla: https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS -[2] Gluster users list ID: gluster-users@gluster.org -[3] Gluster devel list ID: gluster-devel@gluster.org -[4] Gluster users list subscribe/view archives: https://lists.gluster.org/mailman/listinfo/gluster-users -[5] Gluster devel list subscribe/view archives: https://lists.gluster.org/mailman/listinfo/gluster-devel diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE index 0ec6eb319ee..e69de29bb2d 100644 --- a/.github/PULL_REQUEST_TEMPLATE +++ b/.github/PULL_REQUEST_TEMPLATE @@ -1,33 +0,0 @@ -Many thanks for your interest in improving GlusterFS! - -GlusterFS does not use GitHub Pull-Requests. Instead, changes are reviewed -on the Gerrit instance of the Gluster Community at https://review.gluster.org - -In order to send your changes for review, follow these steps: - -1. login on https://review.gluster.org with your GitHub account -2. add a public ssh-key to your profile on https://review.gluster.org/#/settings/ssh-keys -3. add the Gerrit remote to your locally cloned git repository - - $ git remote add gerrit ssh://$USER@review.gluster.org/glusterfs.git - -4. configure the commit hooks - - $ git review --setup - -5. post your changes to Gerrit - - $ git review - - -You may need to install the 'git-review' package if 'git review' is not -available. Note that the hooks for the repository make sure to add a ChangeId -label in the commit messages. Gerrit uses the ChangeId to track single patches -and its updated versions. - -For more details, see the documented development workflow at - http://gluster.readthedocs.io/en/latest/Developer-guide/Simplified-Development-Workflow/ - -If there are any troubles or difficulties with these instructions, please -contact us on gluster-devel@gluster.org or on Freenode IRC in the #gluster-dev -channel. diff --git a/.github/RELEASE_TRACKER_TEMPLATE b/.github/RELEASE_TRACKER_TEMPLATE new file mode 100644 index 00000000000..502bbd5556c --- /dev/null +++ b/.github/RELEASE_TRACKER_TEMPLATE @@ -0,0 +1,12 @@ +<!-- Please use this template while creating a tracker issue --> + +**Description of problem:** +A tracker issue to track the issues that will be fixed as a part of this release + + +**Major or minor release**: + + +**Release version**: + + diff --git a/.github/stale.yml b/.github/stale.yml new file mode 100644 index 00000000000..460e327c6ea --- /dev/null +++ b/.github/stale.yml @@ -0,0 +1,25 @@ +# Number of days of inactivity before an issue becomes stale +daysUntilStale: 210 +# Number of days of inactivity before a stale issue is closed +daysUntilClose: 15 +# Issues with these labels will never be considered stale +exemptLabels: + - pinned + - security +# Label to use when marking an issue as stale +staleLabel: wontfix + +# Comment to post when marking an issue as stale. Set to `false` to disable +markComment: > + Thank you for your contributions. + + Noticed that this issue is not having any activity in last ~6 months! We + are marking this issue as stale because it has not had recent activity. + + It will be closed in 2 weeks if no one responds with a comment here. + + +# Comment to post when closing a stale issue. Set to `false` to disable +closeComment: > + Closing this issue as there was no update since my last update on issue. + If this is an issue which is still valid, feel free to open it. |