Acebanner wrote on Nov 10
th, 2011 at 2:20pm:
When v3.0 is released, will it require 'translating' existing v2.5+ programming, or a reinstallation of a whole new program? How much of a revamping is it really? I have a few Sesame projects I want to tackle in the new few months, and a lot of these v3.0 features would make them a lot easier to implement. If the feature-freeze were implemented tomorrow, how long before we could get our mitts on it? A month? Three months? Six? Just a ballpark estimate.
Sesame3 does require an automatic translation from Sesame2. This is because Sesame3 also supports 64 bit. But, the SBasic is fully back-compatible and does not need to change at all (unless you want to). The translation from 2 to 3, does not require any human intervention or decisions.
If we feature lock today, it will be at least a couple of months to test, fix, and document. Jessica is already plowing through the user manual and making great progress. But there are screen shots, the programming manual, web pages, online docs, packaging, promotion, and etc. that have to be taken care of.
All sorts of ducks must be aligned.