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
  • #21659

Closed (moved)
Open
Opened Mar 06, 2017 by Nick Mathewson@nickm🐙

Prop275: When 0.2.9 is the oldest remaining supported series, make 'published' times uniform

In #21642 (moved), we did the necessary preliminary work to make sure that Tor 0.2.9.x and later could behave themselves when the 'published' date in every consensus document was sent to the future.

When older series are all unsupported, we can finish proposal 275, and set 'published' to e.g. 2038-01-01 00:00:00 in every "r" line in every consensus document.

This change will make consensus diffs much, much smaller.

Leaving in 0.3.2, though 0.3.4 or 0.3.5 seems likelier.

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