Project → v1.1 [week 7]
Overview: update UG and DG in the repo, update project plan in repo, attempt to do global-impact changes to the code base
v1.1 Summary of Milestone
| Milestone | Minimum acceptable performance to consider as 'reached' |
|---|---|
| Team org/repo set up | as stated |
| Project plan formalized | as stated |
| Have done some enhancement to the code | at least attempted to enhance the code of a component, even if you did not fully succeed |
| All project documents updated as required | updated docs are merged to the master branch |
❗️ Reminder: Reaching individual and team milestones are considered for grading the project management component of your project grade (expand the panel below for more info).
v1.1 Project Management
-
Fix any errors in org/repo set up (e.g. wrong repo name).
-
When all changes intended for v1.1 is merged to the master branch, use
git tagfeature to tag the current version asv1.1 -
Start tracking your project schedule using GitHub issue tracker and milestones. More instructions coming soon.
v1.1 Documentation
-
Update User Guide, Developer Guide, README, and About Us pages as described earlier.
Submission: merge your changes to the master branch of your repo.
v1.1 Product
- Each member should try to add some enhancements that are in line with the vision for v2.0. Preferably, these should be
global-impact enhancements, touching as many other components as possible. Refer to the AddressBook-Level4 Developer Guide has some guidance on how to implement a new feature end-to-end.