I concur with Conrad. As I understand it, as long as you stick with
1.2.x versions, there should be no new 'features' to worry about
implementing, only bugfixes. So I'd recommend keeping up with them, and
the 'upgrade' should go smoothly because it's generally not too much of
an upgrade.
I'd recommend you stay away from 1.4.x until you've had ample time to
test it (and it's had ample time to be claimed mature enough for
production). I'm not claiming 1.4.x is not ready for production, I bet
there is a large number of peoples on the list using it happily in
production, but you rightly seem to desire as little trouble as possible
in the upgrade... and the implementation of a few features has changed
considerably in 1.4.
Moj
Conrad Wood wrote:
On Mon, 2006-10-16 at 13:13 +0200, Simone Ruffilli wrote:
at the moment (fortunately) i'm not experiencing any kind of
particular problem, do you suggest me to upgrade asterisk?
#1 sysadmin rule:
If it's not broken, just don't fix it.
That will get you into trouble when it _does_ break.
I rather *test* new versions, fix any configuration problems and then
keep the live versions uptodate.
It can be quite a nightmare to skip lots of versions, particularly under
timepressure with a broken system at hand.
Conrad
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
!DSPAM:500,45336c6c291961385410434!
--
Mojo <[EMAIL PROTECTED]>
Office Manager, Horan & Company, LLC
(907) 747-6666 x112
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
