Create a formal release for distribution

[k8hertweck]

I recommend packaging this software as a release, since we'll be able to track the number of downloads using the GitHub API. This will make it easier to track people using the package as-is (without customization). The alternative is to suggest people download using the "download zip" feature on the main page of the repo. Although this works, we won't be able to track it. Releases also provide a nice way to vaguely track usage of new features, community contributions, etc.

I think the first release at the end of September would work well being labeled as a beta release, indicating it's part of the pilot.

[ergonyc]

This makes sense. What do we need to do besides:

• create the .zip / release
• update the "installation" instructions to download release over devtools::install_github("ergonyc/omicser")

[ergonyc]

Created a "pre-release" v0.1-alpha. Note that the documentation still refers to a devtools::install_github installation.
https://github.com/ergonyc/omicser/releases/tag/v0.1-alpha. DELETED release.

[k8hertweck]

Crap, I didn't think about the interaction between the releases and installation. I'll research this a bit more

[k8hertweck]

Looks like there isn't a straightforward way to use devtools for installation while also tracking downloads. I'll note this in my assessment strategy.

[ergonyc]

I removed the v0.1-alpha release due to it being old/buggy and we have not followed good "release" hygene. Need to revisit install instructions (@k8hertweck )and alpha-release.