[tor-bugs] #9553 [Tor]: Please bump tor version in maint-* branches as part of the release process

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#9553: Please bump tor version in maint-* branches as part of the release process
-------------------------+--------------------------------------------------
 Reporter:  karsten      |          Owner:     
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:     
Component:  Tor          |        Version:     
 Keywords:               |         Parent:     
   Points:               |   Actualpoints:     
-------------------------+--------------------------------------------------
 I just spent an hour wondering why Shadow simulates tor-0.2.4.16-rc just
 fine, but aborts when simulating maint-0.2.4:

 {{{
 0:0:22:976412 [thread-0] 0:5:2:381227791 [scallion-error] [exit8-81.1.0.0]
 [scalliontor_logmsg_cb] int connection_cpu_process_inbuf(connection_t
 *)(): Bug: /home/ubuntu/src/shadow/build/tor/src/or/cpuworker.c:313:
 connection_cpu_process_inbuf: Assertion rpl.magic == CPUWORKER_REPLY_MAGIC
 failed; aborting.
         **aborting**
 }}}

 Turns out there's no bug in tor.  The problem is that Shadow looks at
 Tor's version string in `configure.ac` to decide what code changes to
 apply.  maint-0.2.4 says it's version 0.2.4.10-alpha-dev.  Editing the
 version string in `configure.ac` to 0.2.4.16-rc-dev fixes the problem.

 Would it be possible to bump the tor version in maint-* branches as part
 of the release process?  Is there a document where this step should be
 mentioned, and do you mind me requesting an update if the version string
 doesn't get updated in the future?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9553>
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