Skip to content

Instantly share code, notes, and snippets.

@totherik
Last active August 29, 2015 14:07
Show Gist options
  • Save totherik/b76d17ef3c39f65fde2f to your computer and use it in GitHub Desktop.
Save totherik/b76d17ef3c39f65fde2f to your computer and use it in GitHub Desktop.

Issues

Triage immediately. Overnight issues triaged next morning. Label issues with one of the following:

support The issue is a question about how to use the software.

bug The issue reports a known, reproducible bug in the software.

enhancement The issue requests a feature to be added to the software.

Guidelines

support

Once replied to, if the reporter of the issue does not respond within 7 days, the issue will be closed due to inactivity.

bug

TDB

enhancement

TBD

Pull Requests

Review immediately. Overnight PRs reviewed the next morning. Label PRs with one of the following:

breaking - The code change in the pull request is backward-compatible with the existing published version of the software.

non-breaking - The code change in the pull request is fully backward-compatible with the existing published version of the software.

next-major - The code change in the pull request may be breaking or non-breaking but is intended to be published in the next major release of the software.

next-minor - The code change in the pull request may only be non-breaking and is intended to be published in the next minor release of the software.

next-patch - The code change in the pull request may only be non-breaking and is intended to be published in the next patch release of the software.

experimental - The code change is experimental and is only intended for peer reivew and local testing.

Guidelines

breaking

TBD

@grawk
Copy link

grawk commented Oct 20, 2014

👍 in general..

In addition to having SLAs for triage and follow-up, I would recommend that we either rotate WHO triages on a daily or weekly basis, else break up the modules into owners where each module owner is responsible at all times for that triage

@aredridel
Copy link

Bug: if critical, fix ASAP. If not critical (work-arounds are easy?), fix ASAP but not urgently ;-)

@aredridel
Copy link

enhancement ... I think this is where our process falls down a little. We don't have a concrete idea of what makes a decision 'decided' unless there's a patch and +2. Sometimes it's nice to hammer down "that's a good idea" before actually writing a lot.

@aredridel
Copy link

Triage: next-business-day?

@pvenkatakrishnan
Copy link

I want to second Matt about rotation. Reason being , getting a balance between 'Everyone spends time on the same issue' / 'One person ends up managing most all the time' syndromes. If we are not sure about a specific component, obviously we can reach out to whomever has more experience on those to get a resolution. Also if a person starts answering an issue, they could assume responsibility for getting it closed out (obviously everyone can jump in to give views and close out too).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment