tP: v1.6
What's happening this week:
v1.6
Things to note:
Remind yourself of our policy on reuse (e.g., how to give credit for reused code):
High-level workflow for deciding what to do for each PE-D bug
NotInScope
if the same is reported in the PE (eligibility criteria).The goal of freezing features in the pre-release iteration is to subject the features to at least one round of intensive non-dev testing before they are released to the users. In other words, avoiding behavior changes unless they are strictly necessary, so that we minimize the possibility of introducing more bugs.
In a real project, minor or critical changes might be allowed even near a deadline -- but here, we do not allow any feature changes because it can start us on a slippery slope and many "is this change allowed?" queries. Therefore, v1.6 should not have any behaviors that were not already tested in the ). Hence, the feature freeze comes into effect at the point you released the JAR file that was used for the PE-D.
While the info below provides you what to do and what not to do in v1.6 specific cases, the important thing is to understand and follow the spirit of the feature freeze (i.e., do not change features further; correct unintentional errors only).
Allowed in the v1.6 milestone:
Not allowed in v1.6:
Using 'Planned Enhancements' DG section to counter known feature flaws: Given you are not allowed to fix feature flaws in v1.6, we allow you to optionally add a section named Appendix: Planned Enhancements
to the end of the DG. More details in the panel below:
FAQs on what is allowed during the feature freeze:
Fix bugs that you deem as important enough to be fixed in v1.6. Also keep in mind that bug fixing can cause regressions which you'll have to catch and fix.
Look for more bugs, and fix them too (i.e., don't limit to bugs found in the PE-D only).
Submit peer evaluations for PE-D testers: Submit your peer-evaluation of PE-D testers to indicate how well they helped your team.
Deadline: by Wed, Nov 13th 2359
The submission is to be done via the TEAMMATES system.
Only one team member needs to submit on behalf of the team but discuss among team members first.
Base the evaluation on the quality/usefulness of the bugs reported as well as the quantity.
Here are the two questions you'll need to answer in the evaluation:
PE-D bug titles will be prefixed with tester ID e.g., ([PE-D][Tester A] UG does not load
) to make it easy for you to bugs reported by each tester.
Furthermore, tester ID mapping (i.e., who is Tester A, Tester B, etc.) will be sent to you via email within 1 day after the PE-D.
*-1.pdf
, *-2.pdf
, ...) if you upload a file multiple times. You can safely ignore that suffix.Submissions:
Don't take PDF conversion lightly: To convert the UG/DG into PDF format, go to the generated page in your project's github.io site and use this technique to save as a pdf file. Using other techniques or not following the settings suggested in the given technique can result in issues such as missing background colors, poor quality resolution, unnecessarily large files (the last two can be considered as bugs).
The PDF versions of the UG/DG should be usable by the target readers, even if not as neat/optimized as the Web versions. For example, margins and page breaks need not be optimized, but they should not hinder the reader either. Assume some will occasionally choose the PDF version over the Web version e.g, for printing, offline viewing, annotating etc.
PE uses the PDF versions of UG/DG, not the Web version! Any problems in those PDF files (e.g., broken links, messed up formatting) can be reported as bugs.
Ensure hyperlinks in the pdf files work. Broken/non-working hyperlinks in the PDF files will be considered as bugs. Again, use the conversion technique given above to ensure links in the PDF files work.
PDF files should,
Try the PDF conversion early. If you do it at the last minute, you may not have time to fix any problems in the generated PDF files (such problems are more common than you think).
Side benefits for early submissions: Given that using buffers to reduce the risk of deadline overruns is a learning outcome of this course, we strongly encourage setting an internal submission deadline a few hours earlier than the actual deadline. As an incentive, we plan to perform some checks on early submissions and inform you if we found issues with your submission (e.g., incorrect file name/format), thus giving you a chance to fix them before the deadline and avoid a penalty for it.
You may use automated tools to improve documentation: e.g., tools such as Grammarly may be used to improve the writing quality and find grammar errors.
The icon indicates team submissions. Only one person need to submit on behalf of the team but we recommend that others help verify the submission is in order.
We will not entertain requests to limit late penalties of team submissions to one person even if the delay was one person's fault. That is, the responsibility (and the penalty) for team submissions are to be shared by the whole team rather than burden one person with it.
v1.6
or v1.6b
.[team ID][ProductName].jar
e.g. [CS2103-T09-2][ContactsPlus].jarReminder: double-check to ensure the code attributed to you by RepoSense is correct.
[TEAM_ID][ProductName]UG.pdf
e.g.[CS2103-T09-2][ContactsPlus]UG.pdf[TEAM_ID][ProductName]DG.pdf
e.g. [CS2103-T09-2][ContactsPlus]DG.pdfgithub.io
Ui.png
, AboutUs.md
etc.) on GitHub. Ensure the website is auto-published.Ensure your code is and the code it attributes to you is indeed the code written by you, as explained below:
</>
icon against your name and verify that the lines attributed to you (i.e., lines marked as green) reflects your code contribution correctly. This is important because some aspects of your project grade (e.g., code quality) will be graded based on those lines.