Publish a list of dead/broken (DOA) versions

[Fishrock123]

Somewhere, somehow, or something like it.

Inspired by #4316 (comment)

[rvagg]

We would probably either need an very clear definition of what DOA means or instead make a document that lists known issues with releases. Personally I don't consider 5.2.0 DOA, it just happens to have a bug that would impact a small percentage of users. I'd be fine with documenting that but having to argue whether a release is DOA just because it has a bug that may impact someone seems like rabbit-hole potential to me.

[ofrobots]

@rvagg, 5.2.0 has a repl bug and a bug with debuggers being broken. IMO, the latter is pretty bad as you don't want users to realize at the worst moment (e.g. in production) that they can't debug a problem.

[Fishrock123]

IMO:

1. Doesn't work. (I.e. we broke module and nothing runs or something.)
2. Contains accidental semver-major breaking regressions.

[rvagg]

There's still a fuzzy line here, a lot of our releases have regressions in them, mostly they just affect a small number of users. I don't think we can have a definitive "DOA" list but rather just list known problems with releases. 5.2.0 works perfectly well in production for the vast majority of users, it is not DOA as that would imply it's not usable, _dead_ in fact, and it is not that.