Make a way to update datasheets with each release

[ftyers]

There needs to be a way to incorporate the following information each release:

1. The datasheet template
2. The human-written/community-contributed sections of the previous version datasheet
3. The updated statistics from the release process

For example:
Let's say we are going from version 23.0 of MCV scripted to version 24.0 of MCV scripted, we have the following information:

1. The datasheet template (which may have been updated between the two releases)
2. Either:
   1. A draft datasheet that has been editted by community members to include information about their language and community and was marked as final and uploaded as part of the 23.0 release.
   2. An unchanged draft datasheet from the 23.0 release that was uploaded as part of the 23.0 release
3. A file including updated statistics and demographic information

If there have been no community additions, then the process is:

1. Generate a draft datasheet using (1) and (3)

If there have been community additions, then the process is:

1. Generate a draft datasheet using (1) and (3)
2. Merge in the sections that contain the community information from the previous version into the new draft

Without the ability to do this we will have to throw away either the community additions, or the new statistics/demographic information, neither of which is desirable.

[Pqvqn]

I tried to fix this problem in my current script -- I don't believe there's a good way to merge the community info from a previous datasheet into a new one.
Instead, I made a separate markdown file that's a form for authors to write in. It only has the sections relevant to them
Then to generate the datasheets, I fill in the template with the author file and the stats file. This way we don't have to parse the previous datasheet in order to generate a new one, and the authors hopefully won't be as confused

[ftyers]

That sounds fine to me! Please make sure it works for the datasheets and document it.