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

Re: [tor-bugs] #2620 [Vidalia]: Vidalia 0.2.11 release and future workflow

#2620: Vidalia 0.2.11 release and future workflow
---------------------+------------------------------------------------------
 Reporter:  chiiph   |          Owner:  chiiph      
     Type:  task     |         Status:  needs_review
 Priority:  normal   |      Milestone:              
Component:  Vidalia  |        Version:              
 Keywords:           |         Parent:              
   Points:           |   Actualpoints:              
---------------------+------------------------------------------------------

Comment(by arma):

 I have to agree with chiiph on this one. Once you have more than one
 branch, and you want to move things between them, svn starts to behave in
 really ugly ways. I wasn't a git convert at first, but now I would never
 imagine trying to use svn for this situation.

 Having two different branches was my idea actually -- that way we can keep
 the stable Vidalia stable, and Matt can gate what goes into it, while
 Tomas can have an organized development tree in the unstable branch (and
 we can make testing snapshot packages of it periodically).

 One challenge will be helping Matt feel comfortable reviewing patches from
 within git. But that's one of the easier things to do in git, so I'm
 betting that's a worthwhile tradeoff.

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