I can promise you though that will make a solid attempt to produce a
workable classic version for 2.9 within a reasonable engineering timeframe.
If we can't, it will be because the engineering issues have become
insurmountable since the point at which we resolved to do this. In which
case we would make an announcement of that with a full explanation at the
time. Hopefully though the engineers will be able to resolve this issue
within a reasonable period of time and we will do a successful final build,
fulfill our obligation and move on.
Kevin Miller ~ [EMAIL PROTECTED] ~ http://www.runrev.com/
Runtime Revolution - User-Centric Development Tools
Thank you, Kevin. We read you loud and clear and it is good to know
where we are standing. I truly hope that the technical issues get
resolved since it would make a nice finish. Personally, though, I
don't care whether the last OS9 build is 2.9 or 2.7.5 or 2.8.2. By
this I mean that if there are real problems to make a proper 2.9
version, you could still consider releasing a build which is not
quite on par with 2.9 but packs as many relevant bug fixes as
possible and becomes the dead-end branch of OS9. The only thing I beg
for is that you retain a capability to build a further fix version
should any critical bugs (yes, critical not just any bugs) surface in
that release within reasonable time. It should be possible for RR to
keep one computer with the latest OS9 codebase and its compilation
environment.
Robert Brenstein
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
