Jan Hendrik wrote:
>> That shouldn't be too much of a problem, since you should be
>> committing to SVN before uploading to the FTP anyway.
>
> "Should" is a very good word in this instance - usually such things
> happen if there is a hurry. <G> Just think about this: you edit
> some content and suddenly notice the price lacks a zero at the
> end. Your editing isn't ready for commit, but this price must be
> corrected immediately on the live server, even if this results in a
> half-edited page for a couple of hours.
>
If reliability and having everything version-controlled matters to you,
make it so the only way into production is through the repository. Then
make it so it isn't a lot harder. If you don't have a real QA/testing
team and procedure it can be as simple as a batch file that commits from
the WC where you make changes, then changes directory to another WC used
for staging on the same machine, does an update and transfers those
files to production. This makes sure that you pick up any work done and
committed elsewhere and that if any change causes a problem you can
update the staging directory to a previously known-working revision to
fix things quickly. You might or might not want to bother copying to
tags to track the versions that have been pushed to production.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 16 14:43:56 2007