Les Mikesell wrote:
> Geoffrey wrote:
>
>>>
>>> A branch/tag to release might make sense if you really want to use
>>> svn as the transport to production. Personally, I think it is better
>>> to update a staging site (perhaps just another WC on the box where
>>> you edit), do some testing, then rsync to the production server(s).
>>
>> We do have a development machine. My personal preference was to
>> update from the development to the production by hand, but 'the powers
>> that be' wanted to update via svn.
>>
>
> But development happens in svn, so you should at least use its ability
> to manage versioning instead of blindly updating to someone's latest
> mistake that happens to be in the trunk/head. One approach is to copy
> the trunk to a branch or tag at points where you expect it to be usable,
> then (perhaps after testing...) switch the production copy to that
> version. Meanwhile new mistakes can be committed without breaking
> anything. Other approaches can work too - like updating only to
> specified revision numbers or repeatedly deleting and copying to the
> same tag name so the updating side doesn't need to track the revision or
> name. Unless no one there ever makes mistakes...
We have yet to use the full power of subversion. The primary goal has
been reached, in that we have our code in a code control mechanism.
We fully plan to exploit further functionality in order to better manage
our development environment.
--
Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-04 21:15:27 CET