Conveniently just using a DVCS like git (and allowing public access to the git repository from which you build any binaries) seems to meet your obligation here unless you imagine a legal opponent will convince a court that the resulting metadata doesn't constitute a "prominent notice" carried by the file. All bets are off on language like that where lay people (in this case people who don't read source code for a living) have no intuition about what's intended.
Posted Apr 29, 2010 0:57 UTC (Thu) by JoeBuck (subscriber, #2330)
[Link]
Git certainly has the information about what changed and when, as does any other revision control system, distributed or not. But as soon as you do a release from it, and make a tarball, if that tarball doesn't have changelogs and updated version numbers, you've broken the rules (besides, it's just bad manners and confusing).