Skip to content

Milestone 17: 1.0 Release

Due Date

Monday, April 29
Grading: Team

Description

It will have all the features implemented and have fixed all the bugs in your issues list.

Grading Rubric

F A failed project has show-stopper bugs, or fails to implement some of the client’s (or teacher’s) required core functionality, or is very hard to use for the intended audience. A show-stopper bug is one that makes the program unusable in practice.

A C-level project implements all of the client’s core features and has no show-stopper bugs. It can have small bugs. It can be missing some small required features. It looks OK.

A B-level project does everything as above but does not have any bugs. The UI looks good. Has unit/behavioral tests. The code is commented. The project implements all the required features, but no more.

An A-level project is a professional-quality app, as found in the top-10 list in the app stores. It does everything as above and goes beyond the client’s requirements by implementing one or more “extra” features. It is a pleasure to use and to look at. Has extensive test coverage. The code has great comments that explain what each file does as what each major method does.

Deliverables

To release your code you will:

  1. Create a git tag named v1.0 on the commit that marks the release: git tag v1.0
  2. Push tags to GitHub: git push --tags. Once pushed to GitHub you will find a Release called v1.0 in your repo. If you can’t get tags to work just create the Release called v1.0 with GitHub.

If you have a mobile/desktop app you will:

  1. Upload your binary (.apk .exe, etc.) to the Release.

If you have a webapp you will:

  1. Publish it on the Internet.
  2. 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).
  3. The webapp must be accessible so we can test it.