Put 'latest' release links in place and make sure they always point to the latest release.

[klonos]

From https://github.com/backdrop-ops/backdrop-docker/issues/5 by @pirog

i think kalabox should always grab the latest upstream version of the backdrop image so once that gets rolled in by the docker folks we can stop disseminating less secure versions of your codebase to all the people who are using KB without Pantheon :)

I think that a "static" link like https://backdropcms.org/download/backdrop.zip is in order. It should currently point to https://github.com/backdrop/backdrop/releases/download/1.5.0/backdrop.zip, but in general we should be updating it to point to latest stable.

Very much related: https://github.com/backdrop-ops/backdropcms.org/issues/280

...or we could automate this if possible 😉 : https://help.github.com/articles/linking-to-releases/#linking-to-the-latest-release

[pirog]

@klonos first of all +1 for a latest release download.

For the docker part of this: FWIW it seems to be a docker convention to actually go in and do the manual version bumps (this way we can track/preserve images for every version) instead of relying on a "latest.zip" that we could "set and forget".

[klonos]

https://stackoverflow.com/questions/24987542/is-there-a-link-to-github-for-downloading-a-file-in-the-latest-release-of-a-repo

Seems that there is a way to get to the latest release page, but no way to get the latest release file. So, https://github.com/backdrop/backdrop/releases/latest works, but https://github.com/backdrop/backdrop/releases/download/backdrop.zip not. Hmm.

[ghost]

https://github.com/backdrop/backdrop/releases/latest/download/backdrop.zip links to the latest zip file release.

I think we should link to this instead of the specific version (and have to keep updating it) on the homepage.