Maybe we should create an official end of life deprecation entry before removing. @jasnell WDYT?

Yep, I agree. Let's mark it end of life in docs/api/deprecations.md in 9.0 and look to remove in 10.0.

@cjihrig @jasnell is this really necessary in this case? The old format would immediately be migrated to the new format by starting the repl. So it's a one time process for each user that specifically used io.js 2 and it was already deprecated in io.js 3. It is a history file so would anyone want to rely on a history file that would be two years old?

@cjihrig @jasnell is this really necessary in this case? The old format would immediately be migrated to the new format by starting the repl. So it's a one time process for each user that specifically used io.js 2 and it was already deprecated in io.js 3. It is a history file so would anyone want to rely on a history file that would be two years old?

Since it's a low-risk/low-reward situation, I believe going by the book is just safer... So we'll need to mark it EOL in the docs.

Agree. Let's mark it EOL in 9.x

I rebased this and even though the run-time deprecation did not yet land, I personally feel like it is absolutely fine to directly go to the end-of-life as this does not hurt anyone even in the very unlikely case that someone still uses io.js 2.x and directly updates to 10.x.

CI https://ci.nodejs.org/job/node-test-pull-request/13084/

Landed in 60c9ad7.