possibly archive "old" CHANGELOG.md entries (by year?)

[Fishrock123]

CHANGELOG.md is huge. My local markdown viewer now locks up attempting to preview it. I think we should begin archiving it by year.

cc @nodejs/ctc?

[Fishrock123]

I also just lost a bunch of work to my editor freezing on the preview. 🔥

[rvagg]

Maybe you have too much Atom in your life?

[rvagg]

fwiw I think it'd be fine to archive it by year in the docs directory as long as each doc points to the next at the end.

[ChALkeR]

Previous discussion: #2810.

[ChALkeR]

Actually, splitting per year (and cross-linking them) looks like a much better idea than splitting per major version, so +1 from me on this one.

[Fishrock123]

Maybe you have too much Atom in your life?

I assume there will be a point where GitHub will also simply refuse to render it. :P

[MylesBorins]

+1 on the idea of splitting by year.

[silverwind]

I assume there will be a point where GitHub will also simply refuse to render it

That's at 2 MiB, right? 😈

Anyways, +1 on archiving everything pre-4.0 to a file in doc, possibly linking to it.

[ChALkeR]

@silverwind

Anyways, +1 on archiving everything pre-4.0 to a file in doc, possibly linking to it.

That's by version. Could you clarify, is 2016-02-09, Version 0.12.10 (LTS) pre-4.0 or not? =)

[silverwind]

@ChALkeR Right, that's not going to work with LTS. By age is fine then.

[Fishrock123]

Hmmm, this seems a little more tricky than I had anticipated. Is it possible that pre1.0.0 (i.e. in the 0.6-0.9 era) ordered the changelog by version number and not date? I see some out-of-order entries..

[rvagg]

possible, I'd +1 a reordering if you want to do that

[MylesBorins]

So it looks like our changelog has finally gotten over 1 MB and github is no longer allowing us to view it :sad: