[stp-dev] SVN Structure Proposal for STP

[Andrea Zoppello <andrea.zoppello@xxxxxx>]

Hi All,

Looking at current svn repository organization it seems that now we've 
an organization
where "trunk" "tag" and "branch" are referred to the "whole stp project" 
so we've something like:

svn+ssh://dev.eclipse.org/svnroot/stp/trunk
svn+ssh://dev.eclipse.org/svnroot/stp/tag
svn+ssh://dev.eclipse.org/svnroot/stp/branch


I think that it's better we'll have the trunk/branch/tag structure  for 
each  eclipse subproject,
separately from the main STP as it allows for better control over each 
project.

to be more concise i'll use <stp-svn-root> for the base stp svn url 
svn+ssh://dev.eclipse.org/svnroot/stp

Let's take for examples the STP Intermediate Model Project ( 
org.eclipse.stp.model in SVN )

I would like to have a structure like:
<stp-svn-root>/org.eclipse.stp.model/trunk
-------------------------------------------/org.eclipse.stp.im ( 
Workspace Project )
-------------------------------------------/org.eclipse.stp.im.edit ( 
Workspace Project )
------------------------------------------ /org.eclipse.stp.im.editor ( 
Workspace Project )
<stp-svn-root>/org.eclipse.stp.model/tag
<stp-svn-root>/org.eclipse.stp.model/branch

for other subproject the same structure.

Just have a few minute conversation with a guy in my company ( he's 
managing our svn ) about that
argument ant he confirm me that this is the best organization for 
complex projects/subprojects situations
managed by different actors as it seem to be for the stp project.

In our company we're using that organization at it fit quite well.

Any comments is welcome.


Andrea Zoppello
--

*Andrea Zoppello*
___________________________________________
<www.spagoworld.org>

Spagic Architect
___________________________________________

Architect
Research & Innovation Division
*Engineering Ingegneria Informatica S.p.A.
*
Corso Stati Uniti, 23/C - 35127 Padova - Italy
Phone:  +39-049.8692511    Fax:+39-049.8692566

*www.eng.it                    www.spagoworld.org*