RE: RE: Subproject organization question

> -----Original Message-----
> From: Reedick, Andrew [mailto:jr9445@ATT.COM]
>
> -----Original Message-----
> From: Tad Marko [mailto:tad.marko@bhnetwork.com]
>
> > Projects here contain multiple subprojects, so one has to dig about
> inside
> > of the trunk, branches or tags directories looking for the actual
> project
> > you want to check out since we have these conventional
> directories at
> the
> > top of each project.
>
>
> If they're doing:
> trunk/project1
> trunk/project2
> trunk/project3
> branches/project1/branch1
> branches/project1/branch2
> branches/project2/branch1
> branches/project3/branch1
>
> then yes, that's a pretty gawd awful way of organizing things.
>
>
> > project-->sp1-->trunk-->[eclipse project files and code dirs
> with code]
> > | |->branches-->[copies of trunk]
> > | -->tags-->[copies of trunk]
> > |
> > |--sp2-->trunk
> > |->branches
> > |->tags
>
>
> I'm not an Eclipse jockey, but from what little I've done
> with it, there shouldn't be a problem.
>

This is an interesting layout. Are sp1 and sp2 "service packs"? If so,
I personally would consider these "bugfix branches" and not subprojects
in their own right. I'm always interested in learning differing points
of view on this though. My initial thought is to do something like
this:

Project -->trunk
        |
        |--> branches
                |
                |-> sp1-->main
                        |
                        |-->branches

Where ultimately sp1 is merged back to the trunk, and "main" and
"branches" would handle the nitty-gritty details of the work necessary
on this probably quite large body of work.

What do you think?

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org