Opened 6 months ago

Last modified 5 weeks ago

#30917 needs_revision enhancement

Add instructions for making a new maint branch to, and rename the file

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.4.3.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: sponsor31-maybe, network-team-roadmap-?
Cc: gaba Actual Points:
Parent ID: #30839 Points: 0.5
Reviewer: Sponsor:


When we stop supporting a tor release, we follow the instructions in
But we don't have any instructions for a new maint branch or new release series.

Since the instructions are pretty similar, we should put them in, and then find a better name for that file.

Nick will write up a pad, and then I will put it in the file.

Gaba, I think this could be a Sponsor 31 task, because it is about best practices.

Child Tickets

Change History (8)

comment:1 Changed 6 months ago by teor

Parent ID: #30839#30835

comment:2 Changed 5 months ago by teor

Saving the pad here:

Steps for starting a new maint branch

  1. Ideally, do this immediately after a release.
  1. Start a new maint-x.y.z branch based on master, and a new release-x.y.z branch based on master. They should have the same starting point.
  1. Push both of these branches to the master git repository.
  1. In master, change the version to "0.x.y.0-alpha-dev". Run the script, and commit this version bump.
  1. Tag the version bump with "tor-0.x.y.0-alpha-dev". Push the tag and master.
  1. Open tickets for connecting the new branches to various other places. Some of the children are are an examples of these tickets.
  1. Remove practracker from the check-local Makefile target in maint-x.y.z branch only. Merge to release-0.xy.z but do not forward-port to master.

Finally, make sure this document is up to date with our latest process.

comment:3 Changed 5 months ago by teor

Parent ID: #30835#30839
Status: assignedneeds_revision

Part of #30839

comment:4 Changed 3 months ago by teor

Keywords: network-team-roadmap-september added

comment:5 Changed 2 months ago by teor

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

comment:6 Changed 2 months ago by teor

Type: defectenhancement

comment:7 Changed 2 months ago by teor

Keywords: 041-should removed

comment:8 Changed 5 weeks ago by teor

Keywords: network-team-roadmap-? added; network-team-roadmap-september removed
Milestone: Tor: 0.4.2.x-finalTor: 0.4.3.x-final
Note: See TracTickets for help on using tickets.