Context Navigation

#29010 new enhancement

Reported by:	teor	Owned by:
Priority:	Medium	Milestone:	Tor: unspecified
Component:	Core Tor/Tor	Version:
Severity:	Normal	Keywords:	privcount, 040-unreached-20190109, 041-accepted-20190115, teor-unreached-2019-03-08
Cc:		Actual Points:
Parent ID:	#27908	Points:	3
Reviewer:		Sponsor:

We can do CI for PrivCount using chutney:

If we want to check extrainfo descriptors against PrivCount statistics, we'll need to publish them more often in test networks.

Type:	defect → enhancement

These should all be enhancements

Points:	→ 3

This could take a few days, depending on how much we need to change in chutney.

Keywords:	040-unreached-20190109 041-proposed added
Milestone:	Tor: 0.4.0.x-final → Tor: unspecified

These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.

Keywords:	041-proposed-on-roadmap added; 041-proposed removed
Milestone:	Tor: unspecified → Tor: 0.4.1.x-final

Let's review these tickets at the next meeting using our 041-proposed process.

They're on the roadmap, so the review should focus on ticket size and team capacity (and sponsor expectations).

Keywords:	041-accepted-20190115 added; 041-proposed-on-roadmap removed

These PrivCount tickets are on the 041 roadmap, we accepted their points estimates in 041 without discussion.

Sponsor:	→ SponsorV

Sponsor:	SponsorV → SponsorV-can

Keywords:	teor-unreached-2019-03-08 added
Owner:	teor deleted

Unassign myself from -can tickets.

Milestone:	Tor: 0.4.1.x-final → Tor: 0.4.2.x-final

Move privcount tickets to 0.4.2

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

Sponsor:	SponsorV-can

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Milestone:	Tor: 0.4.2.x-final → Tor: unspecified
Status:	assigned → new

Move privcount tickets from 0.4.2 to "Unspecified"; mark as new.

Note: See TracTickets for help on using tickets.