- Update the UG
- Deliver v2.0 midnight before next lecture
1 Update the UG
- Move the draft UG content into the User Guide page in your repository. Update the content as necessary. If a feature is not implemented in the current version, you can either omit it from the UG or mark it as 'Coming soon' (e.g.,
## Archiving contacts [coming soon]).
As mentioned before, while it is more convenient for one person to update the entire UG, we recommend that each person updates their own part of the docs so that we can easily track the contribution of each member using RepoSense.
Recommended: Divide i.e., work related to the User Guide and the Developer Guidedocumentation work among team members equally; preferably based on enhancements/features each person would be adding e.g., If you are the person planing to add a feature X, you should be the person to describe the feature X in the User Guide and in the Developer Guide.
Reason: In the final project evaluation your documentation skills will be graded based on sections of the User/Developer Guide you have written.
Admin tP: Grading → Documentation
2 Deliver v2.0 midnight before next lecture
- As before, do a release on GitHub and upload the v2.0 jar file.
- IMPORTANT: ensure your jar file was generated using Java 11 and can work on all major OS'es using JDK 11.
Admin tP Contstraints → Constraint-Java-Version
- Wrap up the milestone on GitHub.