Home › Blogs › Tom's blog ›
Well, Ouch, One Step Backwards - Reverting to 4.2 for a day or two

Submitted by Tom on Thu, 01/21/2010 - 21:57.
in

We released OpenCalais 4.3 a day or so ago - and we’ve run into a few issues as we’ve rolled it out into production. We think we have a handle on the fixes needed – but to play it safe we’re going to roll back to Release 4.2 for at least the weekend.
 
Sorry for any inconvenience – but we’d rather play it safe and take a day or two to get things totally in shape.
 
Tom

Bookmark/Search this post with:
  • Delicious
  • Digg
  • StumbleUpon
  • Reddit
  • Technorati

Trackback URL for this post:

http://www.opencalais.com/trackback/62920
Login or Register to post a comment.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

OpenCalais 4.3 is once again live

OpenCalais 4.3 is now up & running on all servers. http://bit.ly/cBHq8k

-Krista
The OpenCalais initiative


KristaThomas Mon, 02/08/2010 - 14:19

Any idea when we might switch back to 4.3?

It has been about 2 and a half weeks since we reverted from 4.3 back to 4.2.. Is there a revised estimate on returning to 4.3?


johnbuuck Mon, 02/08/2010 - 12:44

Great timing!

John -

We have just completed upgrading our servers - 4.3 is online and available.

Let us know (we know you will!) if you encounter any problems.

Regards,


FranSan Mon, 02/08/2010 - 13:21

Request for an "OpenCalais version number" in the API and/or RDF

I understand completely how issues like this can come up, which may require shifting between versions during transition to next version. And for the most part, the code that interacts with the OpenCalais service and parses the resulting RDF shouldn't care. But there are some changes in what can be expected in the RDF responses from one version to the next. Even though I am sure the team is making every effort to make all bug fixes and enhancements completely backward compatible from version to version, inevitably there will arise situations where our code that uses the OpenCalais api will want to do something different depending on some characteristic or issue associated with the OpenCalais version our software is talking to. I haven't spent enough time with the current R4.3 release to know if that applies to this release or not. The self-describing RDF goes a long way toward alleviating such concerns, but there is always the possibility that some fix or enhancement generates different results in one version that should be interpreted differently than in a previous version without an easy way for our software to know which interpretation should be in effect at a given moment.

Can a simple OpenCalais version number(s) be added to the API and/or the RDF?


johnbuuck Fri, 01/22/2010 - 11:45