Hello everyone!
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.
Who should participate? Core Tor developers, obfuscation developers, Tor Browser developers, Hidden Services developers, and of course anyone else
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
* 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
* Priority field: * blocker * critical * major * normal * minor * trivial
* Sponsor field: if it's related to a sponsor deliverable
For 0.2.7 triage we did a few rounds until we ended with a good chunk of work for the release. The release is coming out this month and here is some numbers related to it if you would like to use as a reference: https://storm.torproject.org/shared/TLgTuwGNswrIbfhj9NUctPKj6iG9V7KGHpwy7yzb...
I will send more updates on how this first triage session will be done in Berlin and how we will get remote folks to participate. Also, this does not mean what we do in Berlin is final, things can be refined after too.
Cheers, Isabela
On Thu, Sep 24, 2015 at 7:49 AM, Isabela isabela@riseup.net wrote:
Hello everyone!
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.
Who should participate? Core Tor developers, obfuscation developers, Tor Browser developers, Hidden Services developers, and of course anyone else
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
We usually use "028-triage" here. (No periods.) Feel free to use either spelling. I'll do a batch-modify to condense them into 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
Priority field: * blocker * critical * major * normal * minor * trivial
Sponsor field: if it's related to a sponsor deliverable
For 0.2.7 triage we did a few rounds until we ended with a good chunk of work for the release. The release is coming out this month and here is some numbers related to it if you would like to use as a reference: https://storm.torproject.org/shared/TLgTuwGNswrIbfhj9NUctPKj6iG9V7KGHpwy7yzb...
I will send more updates on how this first triage session will be done in Berlin and how we will get remote folks to participate. Also, this does not mean what we do in Berlin is final, things can be refined after too.
Sounds great! Thanks, Isabela!
Isabela transcribed 3.3K bytes:
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
Thanks for organising this, Isa! <3
- keyword field: 0.2.8.x-triage
I've added 028-triage to many tickets relating to bridges and PTs! \o/
- 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
Did you recently add the "size" field? For some reason, I do not see that field on either #7144 or #7349… perhaps the field was only added for newly created tickets?
…
Err, I just created a new ticket, and I still don't see the size field.
- Sponsor field: if it's related to a sponsor deliverable
(I also don't see the Sponsor field! Did you mean keywords? Do you want there to be fields for this?)
FWIW, I am usually slightly unclear which specific things a particular sponsor will pay for, e.g. I believe that things like #7144 and #7349 very likely count towards SponsorS. However, I definitely don't know how much funds remain for SponsorS (or how much will remain by the time I get to doing a ticket), and so it's difficult to determine several factors related to prioritising, possibly reframing the work in a way that some other sponsor will cover, Just Doing It without getting paid, etc.
(I know that many of these issues will be helped by Isa's Trac improvements, and AFAIK there are plans to discuss at the dev meeting better ways for prioritise devs doing stuff without worrying as much about funder stuffs. Just saying that knowing which funder is paying me for a thing is still hard for me to do.)
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
Hi there!
- 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
Yes, sorry for the mistake. Trac actually says points not size (used to Jira) I would suggest to stick with one type of 'measurement' unit so everyone can understand all the tickets. I don't mind following another
For 0.2.7 we did not go back to the tickets and updated the 'actual points' of it. Which we should do, and we will get there :)
And yes, sponsor field is not there yet (another mistake on my side) but you can add it as a keyword if you wish to. And we can fix that later :)
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-
Isabela -
isis -
Mike Perry -
Nick Mathewson