Comments on: When do you stop teaching that old lolcat new tricks? http://bugblogger.com/when-do-you-stop-teaching-that-old-lolcat-new-tricks-59/ The Bug Labs blog Fri, 19 Aug 2011 03:35:30 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Ken http://bugblogger.com/when-do-you-stop-teaching-that-old-lolcat-new-tricks-59/comment-page-1/#comment-121 Ken Thu, 11 Oct 2007 19:13:29 +0000 http://bugblogger.com/?p=59#comment-121 Shawn and Russell, thanks for your feedback :). I think another factor is the age of your product. Our product is in beta now and has not really been released. I think we have more freedom in determining these requirements. And truly the problem isn't just Eclipse versioning but Eclipse * Platform * OS . Shawn and Russell, thanks for your feedback :) . I think another factor is the age of your product. Our product is in beta now and has not really been released. I think we have more freedom in determining these requirements. And truly the problem isn’t just Eclipse versioning but Eclipse * Platform * OS .

]]> By: Russell Nelson http://bugblogger.com/when-do-you-stop-teaching-that-old-lolcat-new-tricks-59/comment-page-1/#comment-120 Russell Nelson Thu, 11 Oct 2007 17:03:05 +0000 http://bugblogger.com/?p=59#comment-120 Support platforms, not packages. E.g instead of supporting Eclipse x.y, you support Ubuntu Dapper, or Ubuntu Feisty. Good stuff in new versions? Oh well -- it doesn't exist on your platform. Anyelse else invites insanity. Support platforms, not packages. E.g instead of supporting Eclipse x.y, you support Ubuntu Dapper, or Ubuntu Feisty. Good stuff in new versions? Oh well — it doesn’t exist on your platform.

Anyelse else invites insanity.

]]> By: Shawn http://bugblogger.com/when-do-you-stop-teaching-that-old-lolcat-new-tricks-59/comment-page-1/#comment-119 Shawn Thu, 04 Oct 2007 13:33:16 +0000 http://bugblogger.com/?p=59#comment-119 IMHO... When version x.z.* is considered stable, and to support x.y.* causes excessive delays, or major code fragmentation to keep both in line. However you must make sure you don't alienate developers that can't move to the latest version because it does not support their favorite plugin that is commonly used. Obscure things like a ADA plugin could be overlooked, but a SVN, CVS, plugin could be very painful to loose. In the case of Java pre 1.5 support has been let go. However 1.5 is to some degree still on life support, and 1.6 is where the energy of Sun is going. 1.6 is stable and 1.5 compatible, meaning that if you are on 1.5, and had to move to 1.6 you would be ok. Actually if you moved from 1.3 to 1.6 you are not going to incur a great deal of pain. My $.02 -Shawn IMHO… When version x.z.* is considered stable, and to support x.y.* causes excessive delays, or major code fragmentation to keep both in line.

However you must make sure you don’t alienate developers that can’t move to the latest version because it does not support their favorite plugin that is commonly used. Obscure things like a ADA plugin could be overlooked, but a SVN, CVS, plugin could be very painful to loose.

In the case of Java pre 1.5 support has been let go. However 1.5 is to some degree still on life support, and 1.6 is where the energy of Sun is going. 1.6 is stable and 1.5 compatible, meaning that if you are on 1.5, and had to move to 1.6 you would be ok. Actually if you moved from 1.3 to 1.6 you are not going to incur a great deal of pain.

My $.02
-Shawn

]]>