CodingVersion Control - release strategies

 

Press Ctrl+Enter to quickly submit your post
Quick Reply  
 
 
  
 From:  Ben (BENLUMLEY)  
 To:  DSLPete (THE_TGG)     
32877.5 In reply to 32877.3 

Been thinking about that, and from what you've said, it adds the things that I was saying (meaning to say) were lacking in svn.

 

What about clients though? From what I can see, they are all command line based. I could live with that, although browsing the history and writing log messages becomes a bit fiddly (from my experience with svn).

 

But I can't see the other folks where I work dropping tortoisesvn for a command line when they barely use branches. Half the time they don't even bother with SVN at all.

0/0
 Reply   Quote More 

 From:  DSLPete (THE_TGG)  
 To:  Ben (BENLUMLEY)     
32877.6 In reply to 32877.5 
Ha. You need discipline in your ranks :)

We wrote a tiny python app which provides a GUI for those who can't cope with the command line.

You should also check out trac if you've not already. It's version control integration is lurvely. Visual, clickable changesets, source viewing at any revision you want etc etc.

It's the future.
0/0
 Reply   Quote More 

 From:  Ben (BENLUMLEY)  
 To:  DSLPete (THE_TGG)     
32877.7 In reply to 32877.6 

I am already familiar with the joys of trac, yes. I like it lots, particularly the ticketing and updating/closing of tickets with time taken directly from svn commit messages.

 

Presumably it still works fine with repo's used with SVK?

 

But I prefer the "show log" and "repo browser" on tortoise svn. Trac would do fine if i didn't have the tortoise ones though.

0/0
 Reply   Quote More 

Reply to All    
 

1–7

Rate my interest:

Adjust text size : Smaller 10 Larger

Beehive Forum 1.5.2 |  FAQ |  Docs |  Support |  Donate! ©2002 - 2024 Project Beehive Forum

Forum Stats