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
  • Issues
  • #2156

Closed (moved)
Open
Opened Nov 04, 2010 by Sebastian Hahn@sebastian

Time to abandon Tor 0.1.2.x?

I just tested an old 0.1.2.19 Tor, and it doesn't work as a client anymore (it can't bootstrap due to not having enough trusted directories available). We also have just three relays on 0.1.2.19 left, none of which are very big. If we finally manage to declare 0.1.2.x dead, we can drop a lot of old compatibility code from Tor in an 0.2.3.x timeframe. Are there reasons why we should not do this?

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.3.x-final
Milestone
Tor: 0.2.3.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#2156