teor

teor's task page

This page lists the tickets I'll be working on in the next month or two. It's based on the Network Team's Useful Ticket Queries page.

CI Fixes

We prioritise CI fixes over everything else, because we can't do much when CI is broken.

Assigned CI Fixes

These ci-fail tickets are assigned to me, and they are in a status that needs some action from me:

TicketQuery(status!=needs_review

Open CI Fixes

I might be able to help with these ci-fail tickets:

TicketQuery(status!=needs_review

Review CI Fixes

I can review these ci-fail needs_review tickets, our Merge Policy says that anyone can review CI fixes:

TicketQuery(status=needs_review,keywords~=ci-fail,group=component

Merge CI Fixes

I can merge these ci-fail tickets, our Merge Policy says that anyone can merge CI fixes:

TicketQuery(status=merge_ready,keywords~=ci-fail,group=component

Merges

sbws Merges

These merge_ready tickets are in sbws, and I am a maintainer:

TicketQuery(status=merge_ready,component=Core Tor/sbws,group=milestone,format=table,order=changetime,desc=true,col=id

Chutney Master

These merge_ready tickets are in chutney, and I am the maintainer:

TicketQuery(status=merge_ready,component=Core Tor/Chutney,group=milestone,format=table,order=changetime,desc=true,col=id

Fallback Scripts Master

These merge_ready tickets are in fallback-scripts, and I am a maintainer:

TicketQuery(status=merge_ready,component=Core Tor/Fallback Scripts,group=milestone,format=table,order=changetime,desc=true,col=id

Tor Mainline

These merge_ready tickets are in tor mainline, or torspec, and I am a maintainer. I need to check our Merge Policy before merging, if I wrote or reviewed the code.

The current mainline branches are:

0.4.4 - master

TicketQuery(status=merge_ready,component=Core Tor/Tor,milestone=Tor: 0.4.4.x-final,group=milestone,format=table,order=changetime,col=id

0.4.3 Bugs

0.4.3 Must

There's still some time until 0.4.3 goes stable. See the Tor release schedule for details.

These 043-must tickets are assigned to me, and they are in a status that needs some action from me:

TicketQuery(status!=needs_review

These 043-must needs_review tickets are assigned to me:

TicketQuery(status=needs_review,reviewer=~teor,keywords~=043-must,group=milestone,format=table,order=changetime,desc=true,col=id

0.4.3 Should

These 043-should tickets are assigned to me, and they are in a status that needs some action from me:

TicketQuery(status!=needs_review

These 043-should needs_review tickets are assigned to me:

TicketQuery(status=needs_review,reviewer=~teor,keywords~=043-should,group=milestone,format=table,order=changetime,desc=true,col=id

Roadmap

I try to do 2 days of roadmap coding per week. I try to revise roadmap tickets before writing new code: revisions count as part of the 2 roadmap days per week.

These tickets are assigned to me, and they are in a status that needs some action from me:

TicketQuery(status!=needs_review

Reviews

I do as many reviews as I can in half a day per week. If I don't finish all my reviews, I ask other team members for help.

(Or explain why the review is delayed on the ticket.)

Assigned Reviews

These needs_review tickets are assigned to me:

TicketQuery(status=needs_review,reviewer=~teor,group=milestone,format=table,order=changetime,desc=true,col=id

sbws Reviews

These needs_review tickets are in sbws with no reviewer, and I am a maintainer:

TicketQuery(status=needs_review,component=Core Tor/sbws,reviewer=,group=milestone,format=table,order=changetime,desc=true,col=id

Chutney Reviews

These needs_review tickets are in chutney with no reviewer, and I am the maintainer:

TicketQuery(status=needs_review,component=Core Tor/Chutney,reviewer=,group=milestone,format=table,order=changetime,desc=true,col=id

Fallback Scripts Reviews

These needs_review tickets are in fallback-scripts with no reviewer, and I am the maintainer:

TicketQuery(status=needs_review,component=Core Tor/Fallback Scripts,reviewer=,group=milestone,format=table,order=changetime,desc=true,col=id

Backports

I try to backport as many tickets as I can in half a day per week, following the Network Team's backport process.

Some tickets aren't considered for backport:

Mainline Merges: master release tickets are merged by the mainline mergers, so the following milestones are hidden:
- Tor: 0.4.4.x-final
new backports: we try to test code in at least one alpha release before backporting it. You can see all the backports on the Hidden Backports page.

These exclusions will change with every major stable release, and some unstable releases.

Backports That Need Triage

These tickets need backport triage, usually by adding a consider-backport-* tag.

This query shows tickets even if they don't have any backport tags: that's a feature, not a bug. I like to see tickets that are in backport releases (or unspecified), so I can tag them for backport, put them in the right release, or close them.

TicketQuery(status=merge_ready,component=Core Tor/Tor,milestone!=Tor: 0.4.4.x-final,keywords!~=consider-backport,group=milestone,format=table,order=changetime,col=id

Ready to Backport

Here are the merge_ready tickets that can be considered for backport. Some tickets that need triage might also show up in this list.

TicketQuery(status=merge_ready,component=Core Tor/Tor,milestone!=Tor: 0.4.4.x-final,keywords!~=consider-backport-if-needed

Missed Backports

Sometimes tickets are accidentally closed, even though they can be backported. These tickets will appear here: (This query also includes tickets that were backported, but they aren't tagged correctly.)

TicketQuery(status=closed,component=Core Tor/Tor,milestone=Tor: 0.4.4.x-final,keywords=~043-backport

Other Tickets

These tickets are assigned to me, and they are in a status that needs some action from me:

TicketQuery(status!=needs_review

Backlog

I've moved my backlog to teor/Backlog, so it doesn't distract me.

Low Priority

I've put my low-priority tasks on another page, so I don't get distracted by them.