Inventory proposals that need merging into specs ; merge them.

Before we can call 0.3.0 done, we must have the specs up-to-date.

changed milestone to %Tor: 0.3.1.x-final

added component::core tor/tor milestone::Tor: 0.3.1.x-final owner::nickm priority::high resolution::implemented severity::normal status::closed type::task labels

Trac:
Owner: N/A to nickm
Status: new to accepted

I have set the "Finished" status on implemented-but-not-merged-to-spec proposals.

There are currently 18 (!) proposals marked as "Finished".

 FINISHED:
   121  Hidden Service Authentication [in 0.2.1.x]
   151  Improving Tor Path Selection
   155  Four Improvements of Hidden Service Performance [in 0.2.1.x]
   158  Clients download consensus + microdescriptors [in 0.2.3.1-alpha]
   160  Authorities vote for bandwidth offsets in consensus [for 0.2.1.x]
   161  Computing Bandwidth Adjustments [for 0.2.1.x]
   162  Publish the consensus in multiple flavors [in 0.2.3.1-alpha]
   196  Extended ORPort and TransportControlPort [for 0.2.4.x]
   204  Subdomain support for Hidden Service addresses
   210  Faster Headless Consensus Bootstrapping [for 0.2.8.x+]
   217  Tor Extended ORPort Authentication [for 0.2.5.x]
   220  Migrate server identity keys to Ed25519 [for 0.2.x.x]
   232  Pluggable Transport through SOCKS proxy [in 0.2.6]
   235  Stop assigning (and eventually supporting) the Named flag [in 0.2.6, 0.2.7]
   236  The move to a single guard node
   237  All relays are directory servers [for 0.2.7.x]
   244  Use RFC5705 Key Exporting in our AUTHENTICATE calls [in 0.3.0.1-alpha]
   260  Rendezvous Single Onion Services
   272  Listed routers should be Valid, Running, and treated as such [in 0.2.9.3-alpha, 0.2.9.4-alpha]

Trac:
Keywords: N/A deleted, TorCoreTeam201703 added

I just merged 235, 236, 237, and 272 into dir-spec.txt

I just merged 204 into addr-spec.txt.

Dividing up the remainder... I think I am the logical person to do these:

   158  Clients download consensus + microdescriptors [in 0.2.3.1-alpha]
   162  Publish the consensus in multiple flavors [in 0.2.3.1-alpha]
   220  Migrate server identity keys to Ed25519 [for 0.2.x.x]
   244  Use RFC5705 Key Exporting in our AUTHENTICATE calls [in 0.3.0.1-alpha]

These are about weights and timeouts and stuff:

   151  Improving Tor Path Selection
   161  Computing Bandwidth Adjustments [for 0.2.1.x]
   160  Authorities vote for bandwidth offsets in consensus [for 0.2.1.x]

These are about hidden services:

   121  Hidden Service Authentication [in 0.2.1.x]
   155  Four Improvements of Hidden Service Performance [in 0.2.1.x]
   260  Rendezvous Single Onion Services

And these are about PTs:

   196  Extended ORPort and TransportControlPort [for 0.2.4.x]
   217  Tor Extended ORPort Authentication [for 0.2.5.x]
   232  Pluggable Transport through SOCKS proxy [in 0.2.6]

Trac:
Component: Core Tor to Core Tor/Tor

How are we doing on these (for 0.3.0)? Are we about to have another pile of them waiting for us with 0.3.1?

Trac:
Milestone: Tor: 0.3.0.x-final to Tor: 0.3.1.x-final

Replying to arma:

How are we doing on these (for 0.3.0)?

I'll take another look over the list. I think we're going to have to start tracking people down and begging them to merge these and/or update the statuses.

Are we about to have another pile of them waiting for us with 0.3.1?

I hope not; I think I've been more careful than we've been in the past about "make sure there is a spec patch."

I've made child tickets for all the "finished" proposals that were implemented in 0.2.9 or later, on the theory that those are the most urgent and the least forgotten. Let's work through this backlog.

~~Also, I'm seeing a memory leak in the unit tests. I think the problem is that in config_get_file_list(), you need to free file_list using smartlist_free(), not tor_free() ~~

whoops; that was on the wrong ticket :(

Trac:
Keywords: TorCoreTeam201703 deleted, N/A added

I'm going to unparent the children and close this one, since they're tracking this issue now.

Trac:
Status: accepted to closed
Resolution: N/A to implemented

closed

mentioned in issue #22275 (moved)

mentioned in issue #22276 (moved)

mentioned in issue #22278 (moved)

moved to tpo/core/tor#21554 (closed)