I completely agree. I have no problem adapting to the changes - if I knew what the changes were. It's the possibility of unexpected changes not being discovered until we upgrade production servers.
Nate -- Nathan Wells Web Developer [EMAIL PROTECTED] DTN DTN. FARM SMARTER. www.dtn.com -----Original Message----- From: Gaulin, Mark [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2008 3:58 PM To: CF-Talk Subject: RE: What are the Necessary Code Changes for Migrating from 6.1 to 8? The issue is not that there might be problems running the new version, but that the vendor has not properly documented the changes between versions. I don't think they should be required to maintain a "version x to version x + 2" set of issues, but a comprehensive list of compatibility-related changes for "version x to version x + 1" is entirely reasonable to expect. IMHO. Thanks Mark -----Original Message----- From: s. isaac dealey [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2008 4:41 PM To: CF-Talk Subject: Re: What are the Necessary Code Changes for Migrating from 6.1 to 8? > Who releases a major revision of a language platform without a > exhaustive change log? Even Microsoft, who every developer loves to > hate, has this information available for .NET. Adobe is billing CF 8 > as a drop-in replacement for earlier versions of MX. If there's no > other option besides a full regression test or completely reading the > documentation on each and every function and tag (which won't catch > the undocumented changes), then this becomes a major upgrade effort, > rather than a simple task a server administrator to perform on a > Saturday night. Uhh, yeah, things change -- sometimes they break ... I'm not aware of any language or platform for which people just upgrade willy-nilly and expect there to never be any problems. Not every bug or omission is found or reported during the beta process. People who have a good handle on their business will generally upgrade in the middle-range (not the earliest adopters, but they don't wait until several years after there's not been any support for their current version either), perform some basic testing and then spot-repair for other issues when they happen. Often I hear horror stories about companies spending huge amounts of time and money to maintain outdated systems because it would be "too expensive" to upgrade, with the expense usually being attributed to the amount of time required to test & fix their application(s). I doubt the ....NET world is much different. -- s. isaac dealey ^ new epoch isn't it time for a change? ph: 503.236.3691 http://onTap.riaforge.org/blog ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:300896 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
