[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Fwd: Re[4]: public/private commits

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Sun, 27 Sep 2009 19:43:22 -0500

Andrey Dibrov wrote:

>>>> This is really ambiguous to create branch per developer.
>> How so? It keeps everyone's work isolated, which is what you're
>> apparently looking for.
> This is require administrative access to SVN to create a branch or
> maintain it.

No it doesn't, other than than making sure the developers have write access in
the path where you want their development branches.

> A private/public commits shouldn't require them (may be
> require, but only to active this kind of feature).

Branches are the usual/expected solution to this problem. Subversion doesn't
have any public/private concepts. Everything is just a path like any other to
subversion and you can do what you want in terms of content or access control
down any path. There are, of course, conventions for trunk/branches/tags, and
the convention for branches are what you are describing.

>> The danger is that the longer you keep people isolated, the harder it
>> will become to merge changes back together.
> This is doesn't matter, developer can just don't commit a week or
> more, what make commit harder too. Difference is in thing what
> developer now can just store its own source changes on server
> instead of local.

Yes, that's the point of branches - they isolate changes from other copies until
they are merged.

>>>> Developers working together on a project should almost never have a
>>>> need to hide things from each other. It's not good for the team.
>>> Better doesn't see broken sources, than gonna get broken build. Team
>>> shouldn't see private commit, it is useful only for developer who
>>> made it.
>> If each developer is committing to their own branch, who else will see
>> the broken sources/build?
> No one, this is ONLY for store changes, not for apply them.

An occasional broken build during development should not be considered a
disaster, especially when it is the result of different people making different
changes. It is often better to make them visible to everyone so they can agree
on the best solution which may very well not be in the code that you want to
keep isolated.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-28 02:44:22 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.