Milestone 14: Release Candidate 1

Due Date: April 15 @11:59pm
Grading: Team

This release has implemented all the features requested by the client and has no bugs. At least, no bugs that have been detected by your careful unit and behavior testing. Basically, you believe that this release is the final one: no more coding is required. You might, or might not, be proven correct by your customers. We call it a feature freeze, because no more features will be added after this, not even small ones.

This release will also implement a bonus feature. This is a feature that your client did not specifically ask for but that you feel they will want or need. Because you know a lot more about software than your client, and now you know a lot about their domain, you should be able to detect one thing, one feature, that should not be too hard for you to implement but which will make the program 10 times more awesome. If you can't think of anything, just implement a feature that you think would be awesome to have.

Client Review

You will again give this release to your client. You will ask the client to review the app, by the last day of classes. Ask them whether or not they are happy with the resulting app, what features they wish they had, and any problems or suggestions for future improvements. They can provide their feedback directly to me (if they want) or to you. If they send you their feedback you should create an Issue called "Client Feedback" with label:client and paste their feedback in there.


If you have a mobile/desktop app you will

  1. create github release,
  2. name it "RC1",
  3. and upload your binary (.apk .exe, etc.) there.

If you have a webapp you will

  1. Publish it on the Internet.
  2. Create a github release.
  3. Name it "RC1" and
  4. 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).
  5. The webapp must be accessible so we can all test it