I agree with the logic about the zip file. But with other file types (e.g.
JNLP files), deploying and testing really is necessary. See Issue 3296 for a
discussion of this issue.
:D
On Sat, Nov 14, 2009 at 8:01 AM, zwetan wrote:
>
> >
> > Yes, in an ideal world downloads should be immutable. Bu
>
> 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 local
Hi Martin,
I don't represent Google but I was involved in the discussion you point to.
I plan on filing an issue about caching. I said I would do this ASAP but I
have been unwell. I will do my best to create the issue tomorrow (I need to
go to bed now!). Your use case sounds very common to me so i
I see now that there's been another discussion of this issue:
http://groups.google.com/group/google-code-hosting/browse_thread/thread/61b471c6e41cf893#
where this was said:
"Downloads are, by and large, meant to be immutable. It is good to
have
a stable URL for software releases. With this use cas
I've started a new Google Code project and am having a lot of
difficulty with the downloads tab. As I test the download and install
from here: http://code.google.com/p/robotframework-autoitlibrary/downloads/list
on various platforms (WinXP, WinVista, Win7) I'm finding and fixing
problems. Then I
5 matches
Mail list logo
