Re: Subversion and RPG source change management

["Richard Schoen" <richard@xxxxxxxxxxxxxxx>]

You're right.  I probably described it incorrectly initially. I tend to
think about a project subdirectory as its own repository even when it's
contained in a master top level repository. 

Two schools of thought:
1.) Do a new repository for each project. Yuk !!

2.) Do a top level repository with new subdirectories for each project.
I like this method although the subversion version numbers change much
more often :-)

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------

message: 8
date: Mon, 24 May 2010 22:17:23 +0200
from: Arco Simonse <arco400@xxxxxxxxx>
subject: Re: Subversion and RPG source change management

This structure looks okay, it is all in one repository. You were
first talking about different repositories, and if you would create
different repositories each repository will start numbering revision
with 1.


Regards,
-Arco