Keep previous versions of released app

[IanMayo]

It doesn't currently make sense to produce Releases of our app.

But, there would be merit in the build tracking Tagged commits. When this happens, we should put the release into a releases sub-folder, into a folder named the same as the tag.

Aah, I guess the releases folder should be browsable, so we can see the list of releases. Or, we will need to generate/maintain an index.html file that lists them.

Hmm, further thoughts on this:

• we could use a "releases" branch in the repo to store these. It would be good if we could actually show a list of PR titles, each linking to a compiled release of that version.
• we should investigate if it's possible to deploy a version of the app via the Releases page (No, I don't think it's possible: https://developer.github.com/v3/repos/releases/#create-a-release)

Hmm, maybe this could be of value: https://github.com/rafrex/spa-github-pages

Aah, maybe there's an easier way: http://www.evansalter.com/blog/github-pages-and-single-page-apps/

[Morphexe]

I am a bit lost on what you want to achieve with this.
Currently and according to #18, I added auto-deploy to the gh-pages branch (which is used by the GitHub pages), I think this is what you want? Or do you want multiple branches , as in , one per release?

[IanMayo]

Unassign @Morphexe - we'll defer it for the future. The intention here is for us to be able to choose to run past versions of the app - to highlight new features, or investigate the growth of functionality.

So, I'm hoping for an index page that lists versions (maybe also annotated with PRs that contributed to that version). Clicking on a version labels opens that version of the app.