Genete wrote:For linux versions I prefer to provide binaries (universal rpm, deb and targz) from tuxfamily, and leave sf for source and windows binaries.
I think it's better to store linux binaries onsf.net for 2 reasons:
1. Keep everything in the same place is logical.
2. We have unlimited space on sf.net. Considering that there will be lot of more releases... Let's save tuxfamily's resources for other purposes
So my suggestion:
* store release sources and binaries on sf.net
* store temporal
builds (development snapshots) on tuxfamily. But maybe use sf.net for that too? They can be removed anytime...
I have a proposal for folder structure at sf.net:
* "ETL" - for all sources of ETL (without subfolders for each version - this is redundant)
* "synfig" - for all sources of synfig (without subfolders for each version - this is redundant)
* "synfigstudio" - for all sources of synfigstudio (without subfolders for each version - this is redundant)
* "binaries" - for Linux and Windows all-in-one packages
** "binaries/linux" - linux packages
** "binaries/windows" - windows installers
** "binaries/mac" - mac packages (someday)
Also, I think there's no reason to make all-in-one source
packages. That's a wasting of web and time resources and having too much alternatives for downloading the same thing confuses users.
Note to all: please don't forget to replace "https" to "http" in urls.