tP: v1.3
Deliver the features that you planned for v1.3.
In case you didn't pay much attention to this last week, here is another reminder about what you can and can't do during v1.4 _feature freeze.
Have any suggestions to improve AB3?
Now that you have worked with AB3 codebase for a while, if you have any suggestions on how to improve AB3 (for future batches), feel free to post in the AB3 upstream issue tracker.
Examples: places where the design/code can be simplified, hard to understand parts of the code, tips you can share with future batches, ...
This task is time-sensitive. If done later than the deadline, it will not be counted as 'done' (i.e., no grace period). Reason: This is 'an early draft'; if done late, it can't count as 'early'.
Coming soon
.Contacts-Pro-User-Guide.pdf
.docs/index.md
): Update to look like a real product (rather than a project for learning SE) if you haven't done so already. In particular, update the Ui.png
to match the current product ( tips).v1.3.1
.v1.3
is strongly discouraged because if you miss that deadline, your team will not be able to benefit from the PE-D at all. It is better to have an earlier release to fall back on in case that happens.v1.4
two weeks later should be the same as the features tested during PE-D, which is the rationale for the feature freeze anyway.To reduce workload, this deliverable has been removed from tP requirements this semester.
v1.2
,v1.3
.v1.3 features demo
.