Fog Creek Software
Discussion Board

Knowledge Base
Terry's Tips
Darren's Tips


I'm looking at CityDesk as a technical evaluator for our team, and I really like a lot about how CityDesk works.

One missing feature, however, is some sort of version control functionality.  Does anyone have any suggestions or ideas for how to get this to work?

Here are some of my ideas, and I was wondering if anyone has any thoughts...

- CVS directly, perhaps using the WinCVS GUI, to manage files exported. GOOD: Straight-forward. BAD: Requires an additional step for less saavy users.

- Using CityDesk built-in FTP, with server scripts that automatically perform CVS backups on a regular basis.  GOOD: Less work for users than CVS directly. BAD: Still requires FTP publish, and loses a significant amount of CVS functionality.

- Use multi-user mode (and Access?) to perform database-based mirroring or backups to a versioning aware system.  GOOD: Non-trivial work (esp. since we are mostly a Java house), seamless backup for users.  BAD: We wind up building an extensive versioning system (and UI) from scratch.

Anyone have any other ideas?  If there was a post-process trigger in CityDesk that would allow us to trigger a CVS update, that would be ideal...?

Will Iverson
Monday, July 1, 2002

Here are some discussions about version control including a message from Joel about it.

Monday, July 1, 2002

*  Recent Topics

*  Fog Creek Home