[tor-bugs] #15864 [Tor Browser]: Differentiate between build and release sha256sums.txt

[Tor Bug Tracker & Wiki]

#15864: Differentiate between build and release sha256sums.txt
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  tbb-team
  mikeperry              |     Status:  new
         Type:  defect   |  Milestone:
     Priority:  normal   |    Version:
    Component:  Tor      |   Keywords:  tbb-4.5-regression,
  Browser                |  TorBrowserTeam201505, tbb-usability
   Resolution:           |  Parent ID:
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by gk):

 Replying to [comment:3 mikeperry]:
 > Ok. How about sha256sums-presigned-build.txt? And should we just make
 this a step in our release process, or should we update the actual build
 scripts? At this point, I am thinking that the release process update is
 OK, but what about later?

 I think I am fine with any fancy additions to "sha256sums-" if they are
 getting our message to the users. I think we should aim at updating the
 actual build scripts in order to avoid adding another thing we need to do
 manually to the release notes. Having a release process update as a
 stopgap is okay.

 > I also think tor-browser-launcher expects sha256sums.txt to exist. We
 should check with them to make sure they can handle the switch.

 Yes, definitely.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15864#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online