Also, we could host on GitHub at a URL like: https://github.com/cocos2d/cocos2d-x/archive/cocos2d-x-3.16.zip but here would require the developer to run ./download-deps.py. Do you think developers are fine with this step or prefer the full download like we already provide?
This is what I need for a reply:
1. took 15 mins
2. took 8 mins
I am in Xiamen, Fujian, China
took 2 mins 25 sec (BUT it got stuck after 90% on first attempt, on second attempt it downloaded successful)
I am in Ahmedabad, Gujarat, India
I think full download will be good o/w it will increase forum post like zip not working etc etc, and you have to reply to each one that run first ./download-deps.py
I’m from Bergamo, Italy.
They’re more or less the same, around 50 seconds for both (~7 MB/s), but I tried a couple times and sometimes the one from cocos2d-x.org is really slow (like 40 KB/s)
I’ve always wondered why you don’t use github.com for releases? I mean at least as a mirror? Oh, yeah while I think you could’ve just used an installer wrapper around effectively running download-deps.py it would make sense you don’t want that for the main use case since the goal should be to reduce barriers, not add them.
So I guess I’ve just wondered why you don’t use one of the free open source release hosting services?sourceforge.net is still in use, for example. I’m sure there are plenty of others.
(I guess I figured it wasn’t costing much since you were hosting it.)
Why was it that you can’t use github.com, by the way? It appears you can add a large binary just fine? Have you tried this before? I realize it’s not necessarily meant for that, but many apps share binary distributables that way, granted they’re usually much smaller in size (I think).
We don’t limit the total size of your binary release files, nor the bandwidth used to deliver them. However, each individual file must be under 2 GB in size.