Release cycle triage proposal


#21

I try to periodically triage new bugs, making sure that they all have tags. At some point, I had every bug tagged, but then some of them didn’t fit into any tags, and five became thirty, and then I got demoralized. I still try to do it every so often.

I never tried to assign levels to things, but if that’s something we want to do, I can try to do it.


#22

A good approach would be to identify bugs you think are important, then nominate them to specific teams to weigh in on.


#23

Hear, ye! Triage is happening again tomorrow. Same time, same place. See the OP for details.


#24

As we discussed on IRC, I have sometimes considered four categories:

  • Fix it now.
  • Retriage regularly (say, every release).
  • Retriage periodically (as a background task).
  • Do not retriage unless requested to do so. Will get fixed when it gets fixed.

Currently, we don’t have the “retriage regularly category”, I don’t think. I would sort of like to use a milestone-per-release as the “fix it now” category; P-high for retriage regularly; P-medium for retriage periodically; and P-low for “do not retriage unless requested”.

The idea would be that after every release we focus on p-high bugs, than focus on p-medium bugs until the next release.

At some point we also discussed the idea of reviewing issues opened since the last triage meeting and so forth. But I think that would require more regular meetings.

+1


Release cycle milestones and P-high
#25

I agree with this direction, but want to point out that P-high are retriaged every three weeks, and we are cycling through P-medium as well, so they are retriaged regularly.

I will post a thread to irlo suggesting we create release milestones, and define them as ‘must fix right now’; and defining P-high as high-priority per team opinion; both retriaged every 2 weeks in this meeting.

Once complication with this use of release milestones is that the roadmap RFC may end up also using release milestones for estimated goal completion. This means it would have two purposes - critical bugs, and tracking non-critical but expected features. I’m not sure this distinction will matter much as long as we’re continually retriaging them.

I have bumped triage frequency to every 2 weeks.


#26

Release triage minutes 2016-08-25

P-high

P-medium


How the Rust issue tracker works
#27

Next triage is in 90 minutes, according to our new biweekly schedule.


#28

Because several people I want to attend are not available because RustConf, I’ve rescheduled for Tuesday 9/13, same time.


#29

Next triage in 80 minutes.


#30

Release triage minutes 2016-09-13

Stable regressions

Beta regressions

Nightly regressions

P-high


#31

This is coming up again tomorrow, the last group triage before the 1.12 release.


#32

Release triage minutes 2016-09-22

Stable regressions

Beta regressions

Nightly regressions

P-high

Old bugs


#33

Release triage minutes 2016-10-06

Stable regressions

Beta regressions

Nightly regressions

none


#34

Release triage minutes 2016-10-20

Stable regressions

Beta regressions

Nightly regressions

P-high

P-medium


#35

Release triage minutes 2016-11-03

Stable regressions

Beta regressions

Nightly regression

P-high

P-medium


#36

Release triage minutes 2016-11-17

Stable regressions

Beta regressions

None

Nightly regressions

Old bugs


#37

Next triage is tomorrow at this time.


#38

Release triage minutes 2016-12-01

Stable regressions

Beta

Nightly

P-high

Old


#39

Reminder that this is happening again tomorrow.


#40

Release triage minutes 2016-12-15

Stable regressions

Beta regressions

Nightly regressions

Crater beta report

Crater nightly report