On Sun, Jul 12, 2009 at 10:36, Moti Ben-Ari<[email protected]> wrote: > > Hello, > > The "New download" page includes the statement: > "we strongly discourage changing file contents". > > Is this an actual prohibition?
You may do as you please. Just note that links to downloads often end up as URLs all over the web, and people expect them to be more or less immutable once uploaded. The warning is to avoid having something like my_software.zip, whose contents changes as new versions are released. Someone downloading the same URL twice may get different contents, which violates the principle of least surprise. That said, the changelog scenario you propose looks acceptable. However, wouldn't it be better to just keep the Changelog under version control, and link to the copy in Subversion (or Mercurial) directly, rather than posting a mutable download? The changelog file for each version would then naturally end up in the release tarballs. - Dave > > I am asking because there are files that are naturally > "cumulative" like release notes, where the entire history > of the file is always maintained. There is no > reason to maintain and upload separate files: > "release-notes-1-5-3.html"; instead, I would like to > have a single file "release-notes.html" and change its > contents with each version. This would also apply to > a small "readme" file that changes little, if at all, > between versions. > > Thanks > > Moti > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
