Split changelog #2810

Activity

1. ChALkeR

   added

   docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.

   feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.

   on Sep 11, 2015
2. ChALkeR commented on Sep 11, 2015

   

   ChALkeR

   on Sep 11, 2015

   Member

   More actions

   That would produce a lot of files. Also, what is meant by «major version» for older node versions that do not follow semver? We will get dozens of small files and would have to switch between them to actually find anything.

   Are there any specific problems with the changelog being half of a megabyte long?
3. disharmonized commented on Sep 11, 2015

   

   disharmonized

   on Sep 11, 2015

   Author

   More actions

   Okay i got it. At least older node versions (<0.12) could be separated, i think. IMHO anyway
4. ilanbiala commented on Sep 11, 2015

   

   ilanbiala

   on Sep 11, 2015

   More actions

   Honestly, the changelog could probably even be split by 4.0.0 and everything else in a separate one since we're kind of starting a new version line.
5. ChALkeR commented on Sep 11, 2015

   

   ChALkeR

   on Sep 11, 2015

   Member

   More actions

   @disharmonized Atm changelog is ordered by date. «older node versions (<0.12)» are still supported (well, 0.10 is), and a release in 0.10 line would go to the top of the changelog.

   Once again: what's the actual profit in splitting the changelog? Are there any issues with it?
6. disharmonized commented on Sep 15, 2015

   

   disharmonized

   on Sep 15, 2015

   Author

   More actions

   @ChALkeR
   All right, you persuaded me. Just close it.
7. ChALkeR

   closed this as completedon Sep 15, 2015