Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stp-dev] SVN Structure Proposal for STP


Each component inside STP has its own version number and life cycle (but with synchronisation for general release). So, I agree that we need your proposition.

Andrea Zoppello a écrit :
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:


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://

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

I would like to have a structure like:
-------------------------------------------/ ( Workspace Project ) -------------------------------------------/ ( Workspace Project ) ------------------------------------------ / ( Workspace Project )

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
fn:Etienne Juliot
adr;quoted-printable:;;2 rue Robert Schuman;Rez=C3=A9;;44400;France
tel;work:02 51 13 51 42
tel;cell:06 86 78 14 82

Back to the top