Write a guide for groups planning to submit big patches to Tor.

This is a master ticket for a document to explain to people or groups who are thinking of landing large branches in the Tor source. It should explain how to do this in an effective and smooth way, go over our practices, and try to prevent as much frustration as possible.

changed milestone to %Tor: unspecified

added 033-triage-20180320 034-deferred-20180602 034-included-20180328 034-roadmap-master 034-triage-20180328 035-removed-20180711 component::core tor/tor ex-catalyst-20190619 milestone::Tor: unspecified points::3 priority::medium roadmap severity::normal sponsor::3 status::new type::task labels

Marking all tickets reached by current round of 033 triage.

Trac:
Keywords: N/A deleted, 033-triage-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

Trac:
Keywords: N/A deleted, 033-removed-20180320 added

This is on the roadmap for 034.

Trac:
Status: new to assigned
Keywords: 033-removed-20180320 deleted, N/A added
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final
Owner: N/A to catalyst

Trac:
Keywords: N/A deleted, 034-roadmap-master added

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Trac:
Keywords: N/A deleted, 034-included-20180328 added

As Tor's writer, am happy to help in whatever way I can be most useful.

Trac:
Cc: nickm, catalyst to nickm, catalyst, t0mmy

Deferring non-must tickets to 0.3.5

Trac:
Keywords: N/A deleted, 034-deferred-20180602 added
Milestone: Tor: 0.3.4.x-final to Tor: 0.3.5.x-final

These tickets are being triaged out of 0.3.5. The ones marked "035-roadmap-proposed" may return.

Trac:
Keywords: N/A deleted, 035-removed-20180711 added
Milestone: Tor: 0.3.5.x-final to Tor: unspecified

Remove myself from tickets I'm not actively working on.

Trac:
Owner: catalyst to N/A
Keywords: N/A deleted, ex-catalyst-20190619 added

Trac:
Status: assigned to new

changed time estimate to 24h

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