Milestone 13: Beta Release¶
Sunday, March 3.
As with all Releases, you will set up a set of Issues in your GitHub which list all the features you will implement by the deadline. Associate these Issues with the Beta Milestone. We will use these features for grading.
For a beta release we want all, or almost all, of the main features to be implemented. Your app should be usable: no show-stopper bugs, no major crashes. It is OK if smaller features have not been implemented or bugs remain to be fixed. Cosmetic problems are OK.
You will give this release to your client, or to prospective users, and ask them for feedback. You will be happy to implement any new critical features they want, and fix all the bugs they find, before the RC1.
You will add as GitHub Issues any feedback you receive from the client or users. That is, for every feature request they make you will add a new enhancement Issue, for every bug they report add one bug issue. You can later decide if you will implement/fix these or not. But, always add them.
To make a Release you will:
- Create a git tag
named v0.5 on the commit that marks the release:
git tag v0.5
- Push tags to GitHub:
git push --tags. Once pushed to GitHub you will find a Release called v0.5 in your repo. If you can’t get tags to work just create the Release called v0.5 with GitHub.
If you have a mobile or desktop app you will:
- Upload your binary to the Release: .apk for Android, .exe for Windows. If you are targeting iOS then you will be using TestFlight, you must send us an invite by the deadline.
If you have a webapp you will:
- Publish your webapp on the Internet.
- Put the URL of your deployed app in the description textbox for that release. Also, if I need a username/password to access your site make sure you write those down in the textbox, and attach any other files or binaries I might need to test your app (ex, things to upload).
- The webapp must be accessible so we can test it.