On Friday 23 March 2012 15:49:20 Calvin Morrison wrote:
On 23 March 2012 11:46, Dan Youngquist dan@homestead-products.com wrote:
On 03/23/2012 07:14 AM, Marvin L Jones wrote:
I don't want to FUBAR this 'production' workstation -- well, not beyond the usual few glitches.
Then you'll want to be sure to have a good backup of 3.5.12 before you upgrade to 3.5.13. Some of us have had show-stopping issues with 3.5.13 and have had to go back to 3.5.12 or to other DE's until the problems are sorted out.
-- PGP key: http://homestead-products.com/pubkey.htm
Could he upgrade directly to Slavek's packages? I don't see why not.
Because it's a 'production' system.
Whilst I appreciate Slavek's work in finding fixes for some of the problems and making patched versions available I don't want to install unofficial/third-party releases on my production systems.
I have a few systems here that I can use for testing (as and when I get the time to do so) so it's no biggie if I need to change the software repo settings to try new (unofficial/third-party) versions of software on them and/or then possibly run into problems.
However, I wouldn't want to do this on my 'production' systems because not only is there the risk of hitting other problems that stop you working but in making them non-standard you increase the maintenance overhead and also leave yourself open to potential problems in the future when you want to get those systems back on to the official releases; with unofficial/third-party releases you just can't predict what will happen - sure, most of the time there aren't problems but I'm afraid that I've been in this game long enough to have been hit by this.
So it's not because I don't have any faith in Slavek's patched releases that I won't install them on my production systems; it's because, in addition to the risk of 'new' problems, maintaining non-standard production systems takes up production time that you really want to spend on production.
LeeE