Opened 2 years ago

Closed 22 months ago

#18639 closed project (implemented)

Perform a Severe Bug Retrospective for the last few years.

Reported by: nickm Owned by: nickm
Priority: High Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-dos-designs, TorCoreTeam201605, TorCoreTeam-postponed-201604
Cc: Actual Points: 6
Parent ID: Points: 3
Reviewer: Sponsor: SponsorU-can


For every severe bug we fixed in 026 and 027 and 028, let's analyze roughly why it happened, and which programming practices could have prevented it. This will help us identify ways to do 0.2.9 better.

Child Tickets

Change History (10)

comment:1 Changed 2 years ago by nickm

Owner: set to nickm
Status: newaccepted

comment:2 Changed 2 years ago by nickm

I've come up with my list of bugs in a spreadsheet, for bugs fixed in or later. I based this on reading the changelogs. There are 56 bugs I thought were worth including in the analysis here. I'm trying to decide whether to upload the spreadsheet, or tag the tickets on trac.

comment:3 Changed 2 years ago by nickm

I have marked a bunch of tickets with the tag "2016-bug-retrospective."

comment:4 Changed 2 years ago by nickm

Keywords: tor-dos-designs added

comment:5 Changed 2 years ago by nickm

I've started an etherpad for commenting on every single darn ticket. I aim to do 10-15 tickets at a time, so I don't get burned out.

comment:6 Changed 23 months ago by nickm

aaaaand, I've got an analysis for every darn ticket. Now to write a summary-of-findings document.

comment:7 Changed 23 months ago by nickm

Keywords: TorCoreTeam201605 TorCoreTeam-postponed-201604 added; TorCoreTeam201604 removed

April is over; calling these april tickets postponed into may.

comment:8 Changed 22 months ago by isabela

Points: medium3

comment:9 Changed 22 months ago by nickm

Actual Points: 5
Status: acceptedneeds_review

Summary-of-findings document written and circulated to other tor devs for sanity-checking. Will plan to publish once reviewed. (Not making this public yet in case I accidentally left some of the swearing in.)

comment:10 Changed 22 months ago by nickm

Actual Points: 56
Resolution: implemented
Status: needs_reviewclosed
Note: See TracTickets for help on using tickets.