If you’ve fixed an issue with one of your songs, here’s how to get the word out.
- Upload the fixed CON with the same filename as the old one. This will ensure the old d.php link works for the new version.
- Visit the C3 DB editor. This tool lets you change all of your song’s metadata, including version number and the time you updated it.
User: author
Pass: c3auth!
- Click “now” in the Updated On popup, or enter the date/time you uploaded the current version for past changes. We store time down to the minute/second, but the DB only shows the date right now.
- Increment the version number by 1. Ignore any playtesting versions for this — your song’s original C3 release is version 1. Always increment by exactly 1 for each post-release change. (Don’t use “1.1”, or “Release Two”, or whatever. Just 1, 2, 3…)
- Add a BRIEF explanation of what changed in the notes field. One or two sentences, please.
- Save the changes.
Uploading a fix will be communicated to the users in the following ways:
- They can see the date next to a song entry in the DB, and hover over it to see the notes
- They can sort by “updated on” in the DB to see all updates in one place
- All fixes from each week will be reported in the Friday blog posts
Hopefully this will work out. I know that users have no way to see the specific fixes for just the songs they own, or a similar super-helpful solution, but this is fine for now. And yes, I know that song management like this should be in the scheduler, but we’re not there yet.