Remove APIv3 endpoints

Start date

Due date

Description

Before we go ahead and remove the endpoints, we should check diagnostics to see what % of servers are still using the APIv3 endpoints (as of Nov 21st, it's about 20% but only a few servers have upgraded to v4.4).

If it's a large % we might want to consider taking a different strategy, e.g. disabling the APIv3 config setting for everyone in v4.6, but not removing the endpoints until a couple of months later to give them a bit more time for migration.

In addition to removing the endpoints, we should also make APIv3 docs less prominent, with a clear note that it's no longer supported.

QA Test Steps

No testing required

Checklist

Activity

Show:

Lindy Isherwood May 21, 2018 at 5:19 PM

Thanks, closing. Noted no testing required.

Jason Blais November 22, 2017 at 12:28 AM

As chatted on our 1-1 today

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Mana

Assignee

QA Assignee

Reporter

Fix versions

Sprint

QA Testing Areas

API

Checklist

Created November 22, 2017 at 12:28 AM
Updated January 23, 2019 at 1:11 PM
Resolved May 21, 2018 at 1:37 PM
Loading...