I was actually just doing that and going down the list, picking fixes and enhancements that are relevant to our product....by the time I got to 7.3...I came almost the same conclusion that I should just print (all of) them and drop them on his desk..:-)
montaseri@gmail.com ("Medi Montaseri") writes: > I have finally convinced my manager to "consider" the idea of > migrating from 7.2 to 8.2. Obviously he needs an ROI (Return Of > Investment) analysis (in a technical sense). So, I am wondering if > anyone has worked on a similar project where you had to go thru the > release notes and bug fixes to compile such a motivational speech > and willing to share. Otherwise, as many links you can provide > would be nice.
You can simply look at the release notes for 7.3, 7.4, 8.0, 8.1, and 8.2.
Print off the contents of those five URLs, and you'll find somewhere between 40 and 50 pages worth of _brief listings_ of bug fixes and enhancements. Drop that pile of paper on his foot and ask if he thinks it seems heavy enough to seem significant.
Add to that the other folks' arguments:
- There be "database eating bugs" there that be fixed in later releases. - Nobody is interested in supporting problems you have with such an ancient version. -- select 'cbbrowne' || '@' || ' cbbrowne.com'; http://www3.sympatico.ca/cbbrowne/internet.html First Fact About Networks "Pipes can be made wider, but not shorter" -- Mark Miller
---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives?