1
lab07
CS56 F18
Name:
(as it would appear on official course roster)
Umail address: @umail.ucsb.edu section
5pm, 6pm, 7pm
Optional: name you wish to be called
if different from name above.
Optional: name of "homework buddy"
(leaving this blank signifies "I worked alone"

lab07: Leaving a legacy

ready? assigned due points
true Thu 12/06 05:00PM Thu 12/06 07:50PM

You may collaborate on this homework with AT MOST one person, an optional "homework buddy".

MAY ONLY BE TURNED IN IN THE LECTURE/LAB LISTED ABOVE AS THE DUE DATE,
OR IF APPLICABLE, SUBMITTED ON GRADESCOPE. There is NO MAKEUP for missed assignments;
in place of that, we drop the three lowest scores (if you have zeros, those are the three lowest scores.)

What you need to do today in lab:

  1. (1 pts) Fill out the name of ONE team member on this worksheet at the top

  2. (9 pts) Fill in only the team members names that are physically present in lab today (including the name of the person at the top of this sheet. Then fill in your mentor and team name.

    Mentor Team
       
    Team Members (one per blank) Team Members Team Members Team Members
           
           

  3. (10 pts) Locate your feedback repo by visiting http://github.org/ucsb-cs56-f18 and searching for FEEDBACK. If you don’t have access to it, ask your mentor for help.

    • Read through it.
    • You should see feedback from your mentor, detailing the pull requests and issues for which your team is supposed to get credit.
    • Make sure you understand everything that is there, and that the list is a COMPLETE list of everything for which you are expecting to get credit.
    • Make sure the final understanding is RECORDED IN THE FEEDBACK REPO, not just a verbal agreement.
    • When you’ve done that, get your mentor to initial here: ____ and you initial here: ____ and record the date/time here: ____ to indicate that the feedback repo, at that time, is complete and that you accept what is there.

    • If there is any dispute about that, bring it to the instructor’s attention NOW before this lab is done. </li>

    • (10 pts) Now look in the repo and see if your TA (Jinjin or Santha)

      • assigned the final points (i.e. grade our of /1000 plus extra credit out of /100) for your team based on the issues you completed, and the feedback from your mentor, and
      • has recording that feedback IN THE FEEDBACK REPO (not just told you).
      • When that’s done, you initial ____ and your TA initials here:____ and record date/time ____.
      • If you presented in lecture, make sure that 50 pts is recorded by Prof. Conrad near the bottom of the repo.
      • If there is any dispute about that, bring it to the instructor’s attention NOW before this lab is done.

    THEN TURN OVER THE PAGE FOR THE REST OF THE 100 points for this lab.

  4. (20 pts) Now, return to your team, and meet with your mentor. Go through the list of issues for team, one at a time, and have your mentor:

    • CLOSE any issues that are actually fully resolved.
    • If the issue is partially resolved, enter a NEW issue for the unresolved part (that the S19 team will work on), and get the mentor to estimate it.
    • Then, work with the mentor to put in at least 500 points worth of new issues for the S19 team to work on. (If you already have 500 point worth of issues, estimated and ready to go for S19, you are done. Otherwise, work together with your mentor on this until it is finished.

    MENTORS: Add a tag for S19 and, if you don’t already have one, a tag for mentor approved. Use the point value tags, and try to stay with values of 100, 200 and 400 only.

    When this is done, you initial ____ and your TA initials here:____ and record date/time ____.

  5. (50 pts) YOUR LAST RESPONSIBLITY IN THIS COURSE: Make a branch in the ucsb-cs56-f18 version of your repo. Do some final edits in the README.md file of the cs56/f18 directory in your repo. Put in a section called “f18 final remarks” and in it, write a short “note” to the next set of students that will work on this legacy code project.

    Tell them exactly what you think would be helpful for them to know as they start the project: what the code does, what features could be added, what bugs exist, what opportunities for refactoring you see. Also add any advice you have on working with the code you have left them, for with legacy code in general.

    Do a pull request with that, and get the mentor to look at it, and approve that you did it: __

    And you are done!