Expiration on Triaging day(s) #13

Merged
merged 5 commits into from Jun 21, 2017

Conversation

2 participants
Contributor

cpaelzer commented Jun 20, 2017

After discussing with rbasak the current mode of "list all expired" bugs is bad in multiple ways.

  • It is depressing for the current triager, who likely will not handle any of those
  • We need to split this backlog among the server Team, but showing up every day hides what the daily triage duty is responsible for

After this change a Triager will only see those that he needs to take care of.

In many ways this is the same that we had initially with the un-triaged time that we had to cover.
Therefore we track the backlog in the same gdoc where we did already track the general triaging backlog.

cpaelzer added some commits Jun 20, 2017

add triage header
We have explanatory headers, add a similar one for the original
triage bug list.

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
expiration bugs only relative to the triage period
Like we do with the normal bug triage duty.
That way missing your triage for a day will not punt it to the triager
that follows.

Note: backlog needs to be taken care of once, this will be tracked in
gdoc and in the Team IRC meeting.

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
update expiration headers
Update the expiration bug list headers to be clear that they
now are only relative to the bug triaging period.

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
fix help text of --no-expiration
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Contributor

cpaelzer commented Jun 20, 2017

@powersj to be discussed in the IRC meeting today, but please take a look ahead if you can

@powersj powersj merged commit f12ab49 into powersj:master Jun 21, 2017

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment