Pat Farrell wrote:
> Let me add some labels so we can be more precise
> [trunk below my new way]
> [trunk above the usual redbean way]
>> This way you can branch the fnflib without branching fnapp.
> What is the specific reference to "this" the [trunk below] or
> [trunk above]
> I'm not seeing which you are referencing, and can't tell which is true.
> From what I can tell, "tags" are really not important or defined to SVN,
> they are just directories, its the users who layer meaning on top of the
> structure. So it looks to be a six of one, half dozen of the other to me.
> Same with branches, they are a usage convention, nothing more.
> Or am I missing something here?
>> also tag each project individually. While, you can still in theory do
>> it with the second layout... the first layout makes much more sense
>> if you have many projects in a single repository.
> I don't see any difference, or don't understand them. so I'm not seeing
> the "much more sense" that you write about.
>>> Having the [trunk below] always struck me as making them
>>> more visible.
>> They are just as visible the first way above.
> Depends, or perhaps it is all a wash. I'm struggling to understand this.
If everything in your repository is intertwined in a way that you'd
never 'release' a version of one component without all the others,
putting the trunk/branches/tags at the highest level probably makes
sense. On the other hand, if you have components with separate
development and release schedules, it doesn't make much sense to get
tags and branches of a lot of unrelated stuff carried along every time
you want one for a lower level component. The distinction is really
only relevant to what you think of as a separate project or component so
I'm not sure anyone else can help you decide.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-09 21:36:51 CEST