Bryan wrote: Since people pay for CT, they rightly expect a high level of stability and documentation. Adding half-way finished support for Sonar features, or skipping work on the documentation would not be appreciated by CT
customers.Phil replied: I respectfully disagree. Waiting 6 months is unacceptable. Also, you wouldn't be adding as you put it "have way support" if you script up Sonar 8's new plug-ins and document them. That wouldn't be a big deal really. You could then go back to finishing off more complex plug-ins tutorials etc.
Bryan wrote: If CT were that rough around the edges, many people would not see the point in paying for it.
Phil replied: many people won't see the point in paying for it if you don't get out updates in a timely manner. Putting my customer hat on, from the customers stand point, the software developer and distributor have taken their money and put out a product that has at best minimal support in Sonar 8 for new features. From the customers standpoint, they have already paid for development and distribution as the parties involved have already been paid for the product.
I say again, how come I was able to get out .HSC support quickly after the initial Sonar 8 release for Sonar 8's plug-ins and we are still waiting for CT to support them? Sonar 8.5 is out today. Wonder how long it will take Cake Talking to be updated to support that version?
Bryan wrote: Also, I think it would be alright if I remarked that the time that it is taking to release the CT update is a bit beyond just adding support for new features in Sonar 8.31. CT has been going through a significant update, not just a little touch up to be compatible with Sonar 8.31.
Phil replied: incremental updates would still be preferable than a 6 month update. As you know, that's what most other software developers do.
Bryan wrote: CT version numbers follow Sonar version numbers to make it easier to know what CT version is compatible with what Sonar version.
Phil replied: that's fine. So, you could put out an unofficial versions of CT with the letter U after them [U for, unofficial] or, go for releases with an RC and build number like this: CT8.3.1RC1,build 10 etc. Then when the final version is ready you could call it Cake Talking 8.3.1 followed by the last build number or, simply call it Cake Talking 8.3.1.
Bryan wrote: However, if CT used its own version numbering system, then CT9 would be forthcoming.Phil replied: I don't think customers will really care about that, if they have to wait 6 months.
Bryan wrote: I'm looking forward to Bill's public announcement so that we can discuss the details with everyone here.
Phil replied: as am I. Regards, Phil Muir Accessibility Training Telephone: US (615) 713-2021 UK+44-1747-821-794 Mobile: UK +44-7968-136-246 E-mail: info@xxxxxxxxxxxxxxxxxxxxxxxxxxx URL:www.accessibilitytraining.co.uk/
PLEASE READ THIS FOOTER AT LEAST ONCE! To leave the list, click on the immediately following link: ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe If this link doesn't work then send a message to: ddots-l-request@xxxxxxxxxxxxx and in the Subject line type unsubscribeFor other list commands such as vacation mode, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq orsend a message, to ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type faq
