Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BridgeDB BridgeDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • BridgeDBBridgeDB
  • Issues
  • #4380
Closed
Open
Issue created Nov 03, 2011 by Karsten Loesing@karsten

Complete BridgeDB upgrades phase 1

This project ticket replaces the milestone "BridgeDB Upgrades Phase 1" and contains all tickets as child tickets that were assigned to that milestone.

(Milestones are the wrong concept here. It's not a milestone of the sort "let's see which tasks we need to complete before releasing a new BridgeDB version." It's a project with a given scope, and we want to remember which tasks belong to this project.)

Speaking of, which sponsor wants to see this project done, or is it a sponsor Z thing? Maybe we should assign this project ticket to a sponsor milestone, or otherwise we may never finish it.

Assignee
Assign to
Time tracking