[api.met.no] Sunrise v1.0 Prolonging http/200-response until 2016-01-04

[api.met.no mailing list]

Dear users.

We have received a request from a developer depending on the sunrise api v1.0 [0] to prolong the delivery of http/200-responses. Sunrise v1.1 [1] is the new version that is replacing v1.0, and there are only minor changes, so in most cases you will probably be able to upgrade to v1.1 with only smaller modifications. As we have announced that the sunrise v1.0 api is deprecated, the normal behaviour is to deliver http/203 whenever we used to deliver http/200, see general documentation regarding versions [2]. As sunrise v1.0 is scheduled for expiry on 2016-04-04, there is still more than 3 months until the end of life date for v1.0. Our LocationForecast LTS [3] promises at least 3 months of deprecation, and here we have more, so there should be enough time to follow our deprecation scheme with http/203 even if we delay sending http/203 until 3 months in advance. Notice that only our LocationForecast LTS release currently provides such a promise, however now that we have set a date for expiry of sunrise v1.0 I would like to give you (applications developers using our api) sufficient warning ahead of removal by following the deprecation procedure. We are happy to say that we are able to comply with the request and prolong sending http/200 for sunrise v1.0 until Monday 2016-01-04. I will ensure that the necessary code changes reaches our backends soon. We will switch back to our normal/documented deprecation scheme on Monday 2016-01-04. No other products should be affected. This doesn't change the decision that sunrise v1.1 (already available) replaces sunrise v1.0 and that sunrise v1.0 still is scheduled for removal on 2016-04-04.

Please ensure that your applications handle http/203-responses, as this is our way to tell you about deprecation. You probably would like to detect this somehow, so that you becomes aware before a product/version is turned off. We cannot promise that we always will be able to prolong sending http/200 after a product/version is deprecated.

I would like to take the opportunity to remind you about our terms of service [4].


Best regards,

Christian Skarby
IT, MET Norway



References:
[0] http://api.met.no/weatherapi/sunrise/1.0/documentation
[1] http://api.met.no/weatherapi/sunrise/1.1/documentation
[2] http://api.met.no/weatherapi/documentation
[3] http://api.met.no/weatherapi/locationforecastlts/1.2/documentation
[4] http://api.met.no/conditions_service.html