Flagrum Posted April 10, 2017 Posted April 10, 2017 The changelogs never really cover all changes. And I am not even talking about all those smaller fixes that sadly go unnoticed sometimes - but often the changes of a whole module is missing. Sometimes a 3rd party dev did not manage to get their list of changes to ED in time, sometimes they don't even keep track of the changes for their customers at all ... ED, maybe you can change the build process: make it mandatory that any changes to a module that were uploaded to your servers by a 1...2...3rd party dev must contain an updated "changelog.txt". This should help the devs to not forget about the changelog of their respective module and this should also help you, ED, to automatically collect and compile the info for the DCS changelog posting here on the forums.
Buzzles Posted April 10, 2017 Posted April 10, 2017 Having a changelog.txt file wouldn't solve the issue. What you want is a more modern approach to change tracking where commits and Pull Requests (if you're in the Git world) are associated to various User Stories/Bugs/Issues, and then the "whats-in-this-version" notes are compiled from that. I suspect ED probably already do something like this internally. It wouldn't solve the issue of the public patchnotes, which'll be compiled by hand to only include relevent stuff or what ED want to make public at this time. Speaking from experience in software, internal change logging / patchnotes can be rather different from what the customer sees. Fancy trying Star Citizen? Click here!
Recommended Posts