Jan Normann Nielsen wrote:
> We cannot have TSVN telling that a new version is available, then
> install it and find out that it is broken and then have to downgrade it.
> It's a waste of time (and time is money where I work).
Automatically updating software is a PITA.
We had a domain server crash recently because it was (gah..) set to
automatically pull Windows updates from MS, and one of them caused a
blue screen on boot. Yes, the server even rebooted automatically
after it had pulled the update.
If you use TSVN in a corporate environment, you should make sure that
clients only update their software after someone has tested it in your
environment and signalled 'OK' for a release. That goes for *any*
software, not just TSVN.
I'm sorry that I can't offer any specific advice on how to accomplish
this - but I'm sure that there exists software that can help with
this. Probably also exists software that can perform a rollback if
you find a critical problem after deployment, which is bound to be
more useful in smaller companies.
Of course, if you have good suggestions about how TSVN can be improved
to work in a corporate environment, that's a Good Thing! I'm only
saying that you're probably not going to be a lot happier in the long
run if TSVN starts being released on 2 day intervals just because
corporate users find this or that bug particularly annoying in their
auto-updating environment.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Oct 25 11:55:52 2005