Define an EOL for our old api

[usta]

As we already merged and released our v1 api scheme now it is time for us to determine a date for EOL of our old v0 api.
If we wont do it as soon as possible both we and our client/users couldnt see our road and move in right path.

So I suggest we start putting a deprecated notice for our old api calls and mention we will remove it.

Lets set a time line of this :
1- We start to add deprecated notices as soon as possible
2- Lets add a EOL date for our v0

My vote for EOL is to be set as May 27, 2026 (because it is our 7th aniversary of 1st commit of endoflife - May 27, 2019)

[usta]

@captn3m0 @marcwrobel @BiNZGi @hebbet @adriens @endoflife-date/everyone

[captn3m0]

I don't see the need to force a migration yet. We should set a deprecation date when we have a reason to deprecate it (maintainance burden, schema changes etc).

[adriens]

Yup, fixing an eol date would be a really good thing I think, for maintenance purpose but also to avoid feature requests on the deprecated one 💭

[marcwrobel]

So I suggest we start putting a deprecated notice for our old api calls and mention we will remove it.

What do you mean by "putting a deprecation notice on API calls" ?

[usta]

for example returning 299 instead of 200

[usta]

or we can use deprecated flag which exist in openapi

[usta]

or we can add Sunset: to header which can be used too

[marcwrobel]

for example returning 299 instead of 200

That would break the contract, so no.

or we can use deprecated flag which exist in openapi

The OpenAPI contract for v0 is no more referenced on endoflife.date, which means it is hard to find now. I doubt this will be effective.

or we can add Sunset: to header which can be used too

This would require to know the date, and we will likely not have one soon.

[MicahWW]

I've just started playing around with the endoflife API, and I think I stumbled across the v0 API before seeing the v1 API. I later found the v1 API docs and realized that what I was using wasn't documented and I started digging and then found this.

To make sure I understand what the v0 API and the v1 API are, is the below correct?

• v0
  • API docs
  • base URL: https://endoflife.date/api/
• v1
  • API docs
  • base URL: https://endoflife.date/api/v1

[captn3m0]

Yup, that’s correct. Perhaps we should cross link them better

[marcwrobel]

Opened #8732 to make it clearer.