[Tilesathome] 'stable' t at h version

[Carsten Möller]

Matthias Julius schrieb:
> Carsten Möller <cmindividual at gmx.de> writes:
> 
>> Knut Arne Bjørndal schrieb:
>>> On Wed, Aug 27, 2008 at 09:52:36AM -0400, Matthias Julius wrote:
>>>> Carsten Möller <cmindividual at gmx.de> writes:
>>>>
>>>>> If it's stable, just svn-copy it to e.g. \tags\release01
>>>>> It's just a pointer, not a physical copy, so don't worry.
>>>>> Maybe this should be anchored in the config file so
>>>>> one can decide whether he or she wants to render
>>>>> safely or test an experimantal version.
>>>> Currently the client only does 'svn up' for its automatic updates.
>>>> This wouldn't be so simple with each new release being copied into a
>>>> new directory.  It would then need to be told by the server how the
>>>> new release is called and do 'svn switch <new_release>'.
>>>>
>>>> Another approach could be to have the server tell clients to which rev
>>>> to update to and clients then do 'svn up -r<new_rev>'.  This has the
>>>> disadvantage that it makes it impossible to apply a bug-fix to the
>>>> stable version.
>>> It would be much simpler and cleaner to have a single stable directory
>>> that most clients check out, and the clients can then just run svn
>>> up. If you want to test a branch or anything you just "svn switch" to
>>> it.
>>>
>>> Yes, this requires merging, but at least with svk it really easy to do
>>> this.
>>>
>>>
>> Why? You can have two tilesAtHome under different parent directories.
>> Even a structure that I suggested before should work without merging or 
>> switching versions! One for experimental the other for stable.
> 
> When each stable release ends up as a new directory in /tags all
> clients need to switch to that to update.
> 
> Matthias
> 
> _______________________________________________
> Tilesathome mailing list
> Tilesathome at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/tilesathome

No. This is not the way it is done.
The stable version is on the maintenance branch.
This does not change!
The development line remains on the trunk.
If the trunk is stable it will be copied to
tags/releaseXYZ and this release will finally be copied
to the maintenance again.
It's simple.

Regards

Carsten