According to Craig, Sedna Release Appears to be Imminent...
This is, of course, great news for FoxPro developers as they have been waiting (im) patiently for it since October when they released SP2. I had noted it on an earlier post and asked around, finding out that Sedna got put behind VS2008 and SQL 2008 in the "release" queue. (Good to see that Craig is providing more details on it, although an updated EULA from Legal certainly isn't something I hoped to see - what new things could they have possibly put into it from June's CTP?)
But since then, a few regression bugs were found in SP2. I can appreciate wanting to close the door on new VFP development - but with some of the fairly major bugs that were introduced, I hope that either:
a) Sedna includes some fixes for it in the xBase apps (I'm not sure how that would work but if the report Preview engine controls how data is displayed, maybe it could)
b) Sedna includes some hot-fix DLLs
One can only hope.
I am definitely looking forward to some of the new pieces (including the ones they haven't spoken about).
Bill Kuhn notes in his comment on Craig's post that if Sedna is going to require SP2, " Sedna might as well stay off the market until SP2 is usable." I think that may be a bit harsh - as some of the new bugs may not affect the type of application everyone might be building but the one that Cathy has definitely affects how desktop applications that produce reports work. If Microsoft can release patches to fix Office 2003 and then reset them pretty quickly, (and this product is scheduled to be dropped from support by 2014 - one year earlier than VFP 9) - then one can hope they do fix it promptly.
This is, of course, great news for FoxPro developers as they have been waiting (im) patiently for it since October when they released SP2. I had noted it on an earlier post and asked around, finding out that Sedna got put behind VS2008 and SQL 2008 in the "release" queue. (Good to see that Craig is providing more details on it, although an updated EULA from Legal certainly isn't something I hoped to see - what new things could they have possibly put into it from June's CTP?)
But since then, a few regression bugs were found in SP2. I can appreciate wanting to close the door on new VFP development - but with some of the fairly major bugs that were introduced, I hope that either:
a) Sedna includes some fixes for it in the xBase apps (I'm not sure how that would work but if the report Preview engine controls how data is displayed, maybe it could)
b) Sedna includes some hot-fix DLLs
One can only hope.
I am definitely looking forward to some of the new pieces (including the ones they haven't spoken about).
Bill Kuhn notes in his comment on Craig's post that if Sedna is going to require SP2, " Sedna might as well stay off the market until SP2 is usable." I think that may be a bit harsh - as some of the new bugs may not affect the type of application everyone might be building but the one that Cathy has definitely affects how desktop applications that produce reports work. If Microsoft can release patches to fix Office 2003 and then reset them pretty quickly, (and this product is scheduled to be dropped from support by 2014 - one year earlier than VFP 9) - then one can hope they do fix it promptly.
Comments