Technically Kevin turned the old thread into a Poll but your poll is more short and sweet.

I represent that remark!!!      
 
Seriously though, I was not only interested in YES or NO, but also a reason why.
 

Quote from kevind on 03/08/07 at 07:46:21:

 
I'm not saying that your poll was bad. Far from it actually. But his *was* more to the point and I think that what ISTech is most interested in is whether people want them to continue developing Classic (no way) or move to just Evo. Personally, I voted just Evo because I think it's a waste of time to try to even fix bugs in Classic. I'm well aware of the hornet's nest that was the source code for the Classic version and if I were them I wouldn't want to touch that rotting carcass with a 10 foot pole. Still, I certainly understand how current users of Classic would appreciate bug fixes.
 
Most companies drop bug fixing old versions VERY rapidly. You will be hard pressed to see new fixes for old versions of Flash, SurfCam, etc. They only fix the newest version and if you want fixes you'll keep current on version. One might think that unfair as you did pay for the old product but it's just not worth it to try to fix a software version is that outdated. It's way more work and provides basically no new money. And, let's put it this way... The last version of Classic was from 2004 and it is now 2007. There has been three years of fixes and upgrades to a discontinued product. That's about 2 years more than there should have been. I think that bug fixes should usually be free once you buy a product but I see no special reason to even attempt coding support for older revisions of a software product. Granted, take what I say with a grain of salt because I write software too and I know first hand the horror that is debugging. No programmer wants to debug any more than they absolutely have to. Trying to fix multiple software revisions is just a black hole with no center. The developer will end up getting sucked into it with no end in sight. So from my vantage point, I do not want to subject ISTech to that level of Hell. I would rather they concentrate on something that 1:Will make them money and 2: Will most quickly create a minimally buggy product. Goal 1 somewhat naturally leads to goal 2 and goal 2 leads to goal 1. They support each other. Fixing a three year old program that has already been superceded for quite some time is just a dead end. And, as Forest Gump says, that's all I have to say about that.

You could be right. But I still think that what I'm saying makes sense. That it's not reasonable to expect a company to support a long dead version of a software package when new versions are now out. Did DBA Mfg ever make bug fixes for old versions of DBA once they came out with a new version? Why should ISTech?  
 
I don't know how many of their customers are sticking with Classic and how many are on Evo. But I hope most of them are on EvoERP by now. I would think that some sort of promotion would be possible to get the holdouts to transition over. Like maybe give them free updates subscription equal in value to the cost of the upgrade to Evo?
 
One of my big problems with the support of Classic (and this happens in plenty of other situations like this as well - Think Windows) is that supporting the old version (Classic) requires that EvoERP conform to the Classic parameters. Such as, EvoERP can't encrypt passwords because Classic wouldn't understand it then. EvoERP can't change database fields that are also used in Classic. The list goes on. It really is time to quit the heel dragging and just bite the bullet and do what it takes to get everyone onto EvoERP.

I agree with GG.  Think DBA->NG.  They dumped a viable product for a pie-in the-sky product that stinks after at least 3 years work.  Some people are perfectly happy with Classic - it does the job.  Classic needs to be maintained while EVO is being developed.  The market will tell ISTECH when Classic is no longer relevent.  I'd hate to think Lynn would operate the way Mike Hart did and leave hundreds of customers stranded.
 
Tom Dlugosh

1) Freeze Classic's feature set forever.
 
2) Remove Classic from future Evo distros
 
3) Continue to support Classic users with bug fixes (stabilize)  
 
4) Develop new features for Evo~ERP only
 
 
Meanwhile, the user community works on the universal interface (Intra/Internet) so that non-transactional users get their data / reports without noodling around inside Evo. Honestly, I get more complaints from users who are trying to extract data than I do from those who are performing transactions. I thought that my web interface was going to be for customers and vendors, but most of the excitement when I demonstrate new web-based features sounds like, "Oh wow, I can use that myself! It's much easier than getting the tracking number (or whatever) out of Evo!"
 
 

The four steps seem to be a very sound approach for long term planning.  In the short run, however, current iterations need a lot of attention.
 
Tom