Opened 4 years ago

Closed 3 years ago

#20995 closed task (wontfix)

Clean up tickets with incorrect milestones

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


There are multiple tickets that are closed but have incorrect milestones.

One such instance are closed tickets with the Tor: 0.3.??? milestone. The recent renaming of this milestone changed tickets that were closed for years in some cases.

Other instances are closed tickets with the Tor: unspecified and Tor: very long term milestone.

Child Tickets

Change History (4)

comment:1 Changed 4 years ago by dgoulet

Status: newneeds_information

Can you give an example here? This seems quite a tedious job just to clarify closed ticket... ?

comment:2 Changed 4 years ago by cypherpunks

Right before i made this ticket, nickm deleted the Tor 0.3.??? milestone which solved part of the problem. My initial thought for this ticket was changing the milestone of these tickets to the proper milestone in which some of them were implemented. I realize this is too much work for too little gain.

Instead I'd like to suggest to move the tickets from the Tor: very long term milestone to the Tor: unspecified milestone and delete the former. Both milestones are very similar and the later seems to be used more.

comment:3 Changed 3 years ago by nickm

Milestone: Tor: unspecified

comment:4 Changed 3 years ago by nickm

Resolution: wontfix
Status: needs_informationclosed

I don't think we're going to do a systematic revision of all the closed tickets, though we're trying to do better in the future. Unless somebody comes up with an automated way to do so. To find out when a ticket was closed, the changelog and the git history are a better bet.

Note: See TracTickets for help on using tickets.