Due date: March 4 @11:59pm.
All, or almost all, of the main features will be implemented by this date. It should be usable: no show-stopper bugs, no major crashes.
You will give this release to your client 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 RC 1.
If you have a mobile/desktop app you will
- create github release,
- name it "Beta",
- and upload your binary there: .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 it on the Internet.
- Create a github release.
- Name it "Beta" and
- 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