Ideal handling for a CHANGELOG that is larger than Github's (et al.) rendering size? #657
Description
Hi team,
We were wondering if you have some suggestions on how to best deal with CHANGELOGs that have grown to a very large size.
See screenshots here:
Currently considering a 5 year split and interlinking files as our solution.