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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Jun 08, 2011 by Karsten Loesing@karsten

Make labels in relay version graph more useful

Runa says new users have trouble making sense of the labels "0.2.1," "0.2.2," etc. in the relay version graph. They need something like "0.2.1 (stable)" and "0.2.2 (unstable)," or they don't understand the graph.

Here are two ways to implement this:

  • Add labels to the current stable and unstable version in the legend. This might be "0.2.1 (stable)," "0.2.2 (unstable)," and "0.2.3 (experimental)" right now. Don't add labels to older versions. However, this may be confusing if people look at a graph from, say, 2009, seeing 0.2.1 as the "stable" version. Also, we'd have to update the labels whenever a new version becomes stable. A graph from 2009 would look even funnier with 0.2.2 as the "stable" version.

  • Add a comment to the text above the graph saying which versions are stable, unstable, and experimental right now. This works for people reading text, but who does that when there's a graph right below?

Right now I prefer the second approach. Are there other approaches?

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