Typically there are two things that drive me to move code versions, the version I am on is declared end of life, or the new version offers a feature we need to stay competitive, outside of those things I am typically inclined to leave well enough alone and focus my energies on other things. I don't really have a pre-determined time I like to let things idle in the market before I use them, but my general rule of thumb is if I am expanding an older project or adding elements to an already in-production environment I will keep the additions in-line with the version of what is already there. If I am building something new all together I will generally start on the newest there is, and by the time the project is done and out of beta the newest at the time of build will have matured quite a bit. Out of curiosity how many out there do actually have full labs of their environments? I know this is an arena where the full open-source guys have an advantage over those of us using big name vendors, since getting the budget for a pair of SBC's can be hard enough, let alone getting budget for another one just to play with. On Thu, 2009-12-17 at 08:29 -0800, David Hiers wrote:
I've been snooping around our production systems, and the base code version for everything that we run in the call path is between 2 and 3 years old. It is patched to a fare-thee-well, and the stuff runs quite well.
We use only top-tier vendors, yet can't recall ever being happy on code that is less than 1 year old. Too many bleeding edge bugs for my current medication level.
How 'bout you guys? How long do you let a codebase steep before you're happy with running it in production?
Thanks,
David _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops