> > Yes, in an ideal world downloads should be immutable. But this > doesn't allow for the "create a download, try it, oops its broken, fix > it" sequence of typical development activities that I've been going > through with my new project. Sure I could (and have) tested my > download file locally first, but there's nothing like testing in the > real public website 'cause that's what everyone who uses the project > will use.
I really don't get the logic here it's a .zip file you should always test locally before uploading your file, that's it if you wait till your file is online ready to be downloaded to realize that it is broken, there is a problem imho also even for yourself you would want to avoid to download the file to be able to test it, that's the kind of thing that can give you huge development cycle a .zip is a .zip, wether you unzip it after a google code download or locally (because duh you re producing the file) the file and its content should be exactly the same in fact whatever is in the zip should be able to be build from the sources by someone doing a checkout on your repo and running the build (ant, maven, make, etc.) zwetan -- 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 google-code-host...@googlegroups.com. To unsubscribe from this group, send email to google-code-hosting+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=.
