wiki:user/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: As Needed

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

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

Milestone: Tor: 0.2.9.x-final (1 match)

Ticket Summary Status Reviewer Priority Severity Modified
#29437 test-stem times out intermittently reopened Medium Normal 4 days ago

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

Milestone: Tor: 0.2.9.x-final (2 matches)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#30234 Get a stacktrace from tor processes launched by stem assigned Medium Normal 36 hours ago
#30235 Tor hangs when asked to change DisableAllSwap over the control port assigned Medium Normal 2 days ago

Milestone: Tor: 0.4.1.x-final (1 match)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#29645 test.exe hangs on Appveyor CI assigned ahf nickm High Normal 13 days ago

I can review these tor-ci-fail needs_review tickets:

Milestone: Tor: 0.4.1.x-final (1 match)

Ticket Summary Status Owner Reviewer Priority Severity Modified
#30051 Add practracker as a pre-commit and pre-push git hook for frequent coders needs_review rl1987 asn High Normal 38 hours ago

I can merge these tor-ci-fail tickets:

Ticket Summary Owner Reviewer Priority Severity Modified Keywords
No tickets found

Merges: As Needed

Chutney Master

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

Ticket Summary Status Owner Reviewer Priority Severity Modified
No tickets found

0.4.0 bugs: Urgent - 15 April

We're prioritising 040-must tickets in March and April 2019, because we want to release 0.4.0 stable on 15 April. See the Tor release schedule for details.

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

Ticket Summary Status Reviewer Priority Severity Modified
No tickets found

These 040-must needs_review tickets are assigned to me:

Ticket Summary Status Owner Priority Severity Modified
No tickets found

Roadmap: 3 days per week

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

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

Ticket Summary Status Reviewer Priority Severity Modified
No tickets found

Roadmap Backlog

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

Reviews: 0.5 days per week

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.)

These needs_review tickets are assigned to me:

Milestone: Tor: unspecified (1 match)

Ticket Summary Status Owner Priority Severity Modified
#23588 Write fascist_firewall_choose_address_ls() and use it in hs_get_extend_info_from_lspecs() needs_review teor Medium Normal 4 weeks ago

Milestone: Tor: 0.4.1.x-final (1 match)

Ticket Summary Status Owner Priority Severity Modified
#29223 List canonical abbreviations to use in Tor functions and identifiers needs_review nickm Medium Normal 4 days ago

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

Ticket Summary Status Owner Reviewer Priority Severity Modified
No tickets found

Backports: 0.5 days per week

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, alpha, and new stable release tickets are merged by the mainline mergers, so the following milestones are hidden:
    • Tor: 0.4.0.x-final
    • Tor: 0.4.1.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.

Here are the merge_ready tickets that can be considered for backport: (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.)

Ticket Summary Owner Reviewer Priority Severity Modified
No tickets found

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.)

Ticket Summary Owner Reviewer Priority Severity Modified
No tickets found

Low Priority

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

Last modified 4 days ago Last modified on Apr 17, 2019, 7:34:04 AM