Isabela: > We are planing on doing a triage session for 0.2.8 release in Berlin! > Below is some guidance of what you can do to prepare for that, also what > you can do if you are planning on being there but want to help build the > release. > > To help with the triage we are asking everyone to add the following > information to tickets you think should be part of 0.2.8 > > * keyword field: 0.2.8.x-triage I tagged all of the tickets that I've been writing proposals for, and also a few more tickets that have been in the back of my mind for a while but are still not very well specified. I still need to find or file tickets for the following two items: * Defending against Hidden Service Circuit Setup Fingerprinting (the infamous MIT paper). This depends on Proposal #254/Ticket #7028. * Tunneling all directory requests through the main Guard. This depends on #12538. If anyone is aware of tickets for either of these, that would be helpful. I suspect ASN probably filed a ticket for the first one. > * Size field: an estimation of how long you think it will take to get > it done (not counting review time, just execution): > * small < 1 day > * medium < 1 week > * large > 1 week We have the "Points" and "Actual Points" fields for this. "Points" are meant to be any unit of time appropriate for a given trac component, and are the field for the estimate before work begins. "Actual Points" specify the units of time the ticket actually took after completion, for evaluation of estimate accuracy/drift/multiplier. Popular choices for units of time for Points are "minutes", "hours", and "days". https://trac.torproject.org/projects/tor/wiki/org/process/TorAgileProcess -- Mike Perry
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev