Re: Repository structure (project with different sub-projects)

Put the branches/tags/trunk directories in front of the module that
may be released separately from other modules.

If a sub-project is always released as part of the project, then you
should put the trunk/branches/tags directory in front of the project
as a whole and branch the whole project.

Remember that branching in Subversion is a link operation. It takes a
1/2 a second to do, and takes up very little room in your repository,
so branching the whole project even if only a single sub-project has
to be branched is not costing you in time or diskspace, and makes it
easier for someone to work on that branch since all the software is
there.

If your sub-projects are independent of your project and shared
between projects, then make them their own modules and use
"svn:externals" to establish the links.

--
David Weintraub
qazwart_at_gmail.com
On Wed, Aug 6, 2008 at 1:55 AM, MarcoE <marco.ehmke_at_ruf.ch> wrote:
>
> Hi all,
>
> I've read different topics how to structure the repository and how to create
> a software release. (trunk/branch/tag)
> But there is a question I couldn't find an answer or recommendation.
>
> The product/project I want to manage in subversion, is quite complex and has
> different sub-projects. Also a sub-project can have different sub-projects..
>
> My Problem: How to manage the version control of the different sub-projects,
> how to structure the repository?
>
> A small example, perhaps than it's more clear where my problem is:
> [code]
> my-repository
> !
>  + product-1
>  !      +-- sub-project-X
>  !      !          +-- sub-project-X1
>  !      !                 ....
>  !      !          +-- sub-project-X2
>  !      !                 ....
>  !      !          +-- sub-project-X3
>  !      !                 ....
>  !      !
>  !      +-- sub-project-Y
>  !      !          +-- sub-project-Y1
>  !      !                 ....
>  !      !          +-- sub-project-Y2
>  !      !                 ....
>  !      !          +-- sub-project-Y3
>  !      !                 ....
>  !      ...
>  !...
> [/code]
>
> Normally following structure is used for "version management", the structure
> "trunk" "branch" and "tag" is used:
> [code]
> my-repository
> !
>  + product-1
>  !      +-- trunk
>  !      !       +-- sub-project-X
>  !      !       !          +-- sub-project-X1
>  !      !       !                 ....
>  !      !       !          +-- sub-project-X2
>  !      !       !                 ....
>  !      !       !          +-- sub-project-X3
>  !      !       !                 ....
>  !      +-- branch
>  !      !       !          ...
>  !      +-- tag
>  !      !       !          ...
>  !      !...
> ...
> [/code]
>
> But how to handle bugfixes for sub-projects? How to create a new release for
> a sub project?
>
> For example I create a patch for "sub-project-X1", how to manage the release
> management?
> It makes no sense to create an new release for the complete product, perhaps
> other sub-projects are still in work.
>
> Can please somebody give me a hint or suggestion how to manage this
> situation and how to structure the repository? It's not really an unusual
> requirement, but I couldn't find a recommendation and currently I don't know
> what makes sense, how to structure the repository.
>
> Best regards
> Marco
>
> Best regards
> --
> View this message in context: http://www.nabble.com/Repository-structure-%28project-with-different-sub-projects%29-tp18844825p18844825.html
> Sent from the Subversion Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org