Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Wiki
    • Org
    • Teams
    • Networkteam
    • Coretorreleases
  • 043Status

Last edited by Alexander Færøy Jun 15, 2020
Page history

043Status

Release 0.4.3 Task Status

PageOutline

Tor 0.4.3 is due on April 15, 2020.

This page lists the remaining tickets for Tor 0.4.3. They are all tagged 043-must or 043-should.

A "must" ticket is one that would block release if we did not have it done by 15 April. A "should" ticket is one that we need to work on, in order to conform to our best development practices.

It's based Teor's page for 0.4.2 status.

Unassigned tickets

These open tickets are tagged 043-must or 043-should, and they don't have an owner.

Please take the ones you can do. Otherwise, nickm will assign them to the best person to fix or triage the ticket.

TicketQuery(status!=closed,owner=,milestone=Tor: 0.4.3.x-final,keywords~=043-must

Triage Tickets

These open tickets are marked 043-must or 043-should, but they are not in 0.4.3:

TicketQuery(status!=closed,keywords~=043-must

Owner Action tickets

These tickets are tagged 043-must or 043-should, they have an owner, and they are in a status that needs action from the owner.

Anyone can change the assignments:

  • assign themselves one of these tickets,
  • un-assign ticket from themselves, or
  • ask someone else to take one of their tickets.

You can also decide that a ticket is not a must-do or should-do for 0.4.3, and defer it. If so, make sure you explain why on the ticket.

TicketQuery(status!=needs_review

Needs Review tickets

These tickets are tagged 043-must or 043-should, and they are in needs_review.

TicketQuery(status=needs_review,keywords~=043-must

Merge Ready tickets

These tickets are tagged 043-must or 043-should, and they are in merge_ready.

TicketQuery(status=merge_ready,keywords~=043-must

Tickets slated for removal from 043

These tickets, in spite of being in the 0.4.3 milestone, are likely to miss 0.4.3 because they are not "must" or "should" or even "can".

TicketQuery(status!=closed,keywords!~=043-must

Clone repository
  • AnonOnWikiFavs
  • AppArmorForTBB
  • AutomationInventory
  • BadContent
  • BlockingBittorrent
  • CI
  • CamelCase
  • CrowdfundingHS2015
  • FlashProxyFAQ
  • FlashProxyHowto
  • FlashProxyUsability
  • HTTPSEverywhere
    • SSLObservatorySubmission
  • ImportantGoogleChromeBugs
  • InterMapTxt
  • InterTrac
View All Pages