title: Version control for Smalltalk / Seaside?
body: <p>I'm primarily a Java EE developer.  I've been asked to explore the possibility of using Smalltalk / Seaside in an upcoming web project.  As you can imagine, this has led to many interesting questions.</p>
  
  <p>How does a team of developers implement software versioning and revision control with Smalltalk / Seaside.  Can you use Subversion or Git?</p>
  
  <p>From what I understand, Smalltalk uses an image rather than saving each class to it's own file.  How does that affect the ability to manage source code revisions, particularly across a team?</p>
  
  <p>Many thanks for any insight you can provide!</p>