Opened 8 years ago

Closed 8 years ago

Last modified 6 years ago

#2682 closed task (implemented)

document Roger's Tor release process and release notes process

Reported by: arma Owned by: arma
Priority: Medium Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If Nick is to start putting out 0.2.2.x tarballs, I need to document my process for putting together a release. A subset of that is my process for writing up a changelog entry.

I think doc/HACKING is a fine location for these guidelines.

Child Tickets

Change History (5)

comment:1 Changed 8 years ago by arma

I put the general release process into doc/HACKING in maint-0.2.2 and beyond, in git commit
dbd4a017560083

I should work on guidelines for creating the ChangeLog stanza and release blurb next.

comment:2 Changed 8 years ago by nickm

Milestone: Tor: 0.2.2.x-final
Status: newassigned

comment:3 Changed 8 years ago by arma

Resolution: implemented
Status: assignedclosed

Nick did it once (for 0.2.2.25-alpha), and took notes in doc/HACKING. It's not perfect, but I'm unlikely to make it better by myself. Now it's up to Nick to do it his way and see if I think of any more.

comment:4 Changed 6 years ago by nickm

Keywords: tor-client added

comment:5 Changed 6 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.