github.com/galamsiva2020/kubernetes-heapster-monitoring@v0.0.0-20210823134957-3c1baa7c1e70/docs/maintenance.md (about) 1 Heapster Maintenance Procedures 2 =============================== 3 4 Triage 5 ------ 6 7 Triage is done on a weekly rotation by members of the 8 @kubernetes/heapster-maintainers team. Initially this will be limited to 9 the following people: 10 11 - @piosz 12 - @directxman12 13 14 The on-duty triage maintainer is responsible for initial triage of bugs 15 and pull requests (labeling, assigning, etc), initially responding to 16 issues, merging pull requests approved by sink owners, and reviewing 17 non-sink-specific pull requests. 18 19 ### Labels ### 20 21 Each issue and pull request should be assigned one of: 22 23 - bug 24 - enhancement 25 - question 26 - support 27 - testing 28 - invalid 29 - docs 30 31 A priority label should also be assigned (`Priority/P[0-3]`, with `Priority/P0` 32 being the highest priority) for `bug` and `enhancement` issues and pull 33 requests. 34 35 Duplicate bugs should be tagged with `duplicate`, and should have a comment 36 referencing the main bug. `wontfix` may be applied as appropriate for issues 37 which won't be fixed. 38 39 Additionally, a sink label should be applied to sink-related issues and pull 40 requests (`sink/$SINK_NAME`). 41 42 Sink Maintenance 43 ---------------- 44 45 Each sink will have a set of one or more owners who are responsible for 46 responding to issues and pull requests, once triaged. If a sink has no owners, 47 a call will be put out for owners, and if none are found, the sink may be 48 subject to deprecation and removal after a release. 49 50 See the [sink owners](sink-owners.md) reference file for more information. 51 52 Releases 53 -------- 54 55 Releases will be performed by @piosz. Any issues about releases should be 56 assigned to him. Version needs to be updated in the `Makefile`, and in the 57 individual YAML files in `deploy/kube-config/` once the images have been 58 built.