So you're about to release your own fork, eh?
Did you....
- ...make sure any additional libraries or code fragments you linked in were GPL compliant?
- If it doesn't come with the OS or the compiler, the license needs to be compatible with the GPL.
- ...tag the version as modified?
- You need to edit the version block resource, the string table, and the about and welcome dialog boxes.
- ...change the contact address?
- Check the welcome dialog box, the about dialog box, the crash dialog box, and the help file entry for crash help.
- ...build the right version?
- You need at least one of the release builds, and if you only built Release ICL, you need to make sure people know it requires SSE2.
- ...build a source archive?
- Just zip all the source files.
- ...remove your debugging code?
- It's embarrassing to have your build crash on a hard breakpoint. WinDiff your tree against the official VirtualDub distribution to make sure you aren't releasing more changes than you intended.
- ...do basic beta testing or QA?
- Well, at least more than the five minutes I usually do.
- ...check the size of your archives?
- Make sure you didn't include a .pdb or other large file by accident.
-- Avery Lee <phaeron@virtualdub.org>