[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #17530 [Tor Browser]: Update release process documentation for hardened Tor Browser

#17530: Update release process documentation for hardened Tor Browser
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  gk
     Type:  enhancement                          |         Status:  closed
 Priority:  Medium                               |      Milestone:
Component:  Tor Browser                          |        Version:
 Severity:  Normal                               |     Resolution:  invalid
 Keywords:  TorBrowserTeam201511R,               |  Actual Points:
  GeorgKoppen201511                              |         Points:
Parent ID:                                       |
  Sponsor:                                       |
-------------------------------------------------+-------------------------
Changes (by gk):

 * keywords:  TorBrowserTeam201511, GeorgKoppen201511 =>
     TorBrowserTeam201511R, GeorgKoppen201511
 * status:  needs_review => closed
 * resolution:   => invalid


Comment:

 On a second thought, there should be no need for a special treatment of
 hardened releases here at all. If there are things that need to get merged
 into the hardened-builds branch then this should get done right after they
 got committed to master. All that remains then is the usual boilerplate
 stuff that is already codified in the release process documentation and is
 done after checking out the proper branch to build from.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17530#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs