Because of the possibility of different CTAN and manual install releases, it's possible that there would be two "Unreleased" sections in the CHANGELOG.md on the develop branch: one for the changes which can be pushed to ctan between TeXLive releases (and which were originally made on the current release- branch) and one for changes which cannot (and which were originally made on the develop branch.
We should probably differentiate these sections (perhaps by changing the second "unreleased" to either "ctan" or "develop", as appropriate).
Additionally VersionManager.py needs to have its handling of this situation improved.
I've done the rearranging of the CHANGELOG sections on the ctan and develop branches as part of the 5.1.0 release. VersionManager.py still needs to be modified to account for this.
Because of the possibility of different CTAN and manual install releases, it's possible that there would be two "Unreleased" sections in the CHANGELOG.md on the develop branch: one for the changes which can be pushed to
ctan
between TeXLive releases (and which were originally made on the currentrelease-
branch) and one for changes which cannot (and which were originally made on thedevelop
branch.We should probably differentiate these sections (perhaps by changing the second "unreleased" to either "ctan" or "develop", as appropriate).
Additionally
VersionManager.py
needs to have its handling of this situation improved.