Re: Please add additional download link
Posted: Tue Jan 27, 2015 2:06 pm
Hi!
Please check out bundled-libs/create-release.sh - that is what gets performed on the release files for i.e. creating checksums, and that's a step that github release cannot offer, and also is why I would not like to advertise the ZIP-tarball by Github. Of course people can use that, but I will not advertise them on the s9y download page.
As for your kind offer of a download server: I would rather like to rely on specific release file hosting; private or custom root servers can easier be compromised, or they go down when people leave the project, so I'd rather not create a dependency on that.
Having a bad "2.0" tag for the release is problematic, it was just too much overhead at the day of release to re-add the tag everytimg I had to create a new download link (had to release 4 times actually). Now we already have a differing 2.0 branch that is more a 2.0.1, so I cannot simply tag that as 2.0. This means, I don't know how to properly tag "2.0" with the contents of the release file without fucking things up.
I think we can discuss this much more easily on the meetup in a few weeks to clarify somethings, and see where we could improve what. Sadly, tagging was always one of my shortcommings that get lost in the heat of release-battleing.
Best regards,
Garvin
Please check out bundled-libs/create-release.sh - that is what gets performed on the release files for i.e. creating checksums, and that's a step that github release cannot offer, and also is why I would not like to advertise the ZIP-tarball by Github. Of course people can use that, but I will not advertise them on the s9y download page.
As for your kind offer of a download server: I would rather like to rely on specific release file hosting; private or custom root servers can easier be compromised, or they go down when people leave the project, so I'd rather not create a dependency on that.
Having a bad "2.0" tag for the release is problematic, it was just too much overhead at the day of release to re-add the tag everytimg I had to create a new download link (had to release 4 times actually). Now we already have a differing 2.0 branch that is more a 2.0.1, so I cannot simply tag that as 2.0. This means, I don't know how to properly tag "2.0" with the contents of the release file without fucking things up.
I think we can discuss this much more easily on the meetup in a few weeks to clarify somethings, and see where we could improve what. Sadly, tagging was always one of my shortcommings that get lost in the heat of release-battleing.
Best regards,
Garvin