Table of Contents

1. Coding Week 1: May 28-June 3
2. Coding Week 2: June 4-June 10
3. Coding Week 3: June 11-June 17
4. Coding Week 4: June 18-June 24
5. Coding Week 5: June 25-July 1 (first evaluation June 24-28)
6. Coding Week 6: July 2-July 8
7. Coding Week 7: July 9-July 15
8. Coding Week 8: July 16-July 22
9. Coding Week 9: July 23-July 29 (second evaluation July 22-26)
10. Coding Week 10: July 30-August 5
11. Coding Week 11: August 6-August 12
12. Submit code and evaluations: August 13-August 21 (final evaluation …

Coding Week 1: May 28-June 3

• Add multi_glass_remoteprog_glass harness backend.

Coding Week 2: June 4-June 10

• start working on adding generated databases support to backendmanager_remoteprog, backendmanager_remotetcp and backendmanager_honey.

Coding Week 3: June 11-June 17

• open PR adding timer to track slow tests.
• finish working on adding generated db support to the harness backends.

Coding Week 4: June 18-June 24

• Get timer and generated PRs merged.

Coding Week 5: June 25-July 1 (first evaluation June 24-28)

• Try to understand code related to matcher.

Coding Week 6: July 2-July 8

• Try and fix bugs in the matcher code for merging msets.

Coding Week 7: July 9-July 15

• Work on bugs.

Coding Week 8: July 16-July 22

• XFAIL the remaining bugs.
• Add multi_remoteprog_glass backend which uses a db with remote + remote shards.

Coding Week 9: July 23-July 29 (second evaluation July 22-26)

• Rewrite cleanly the code for the new backends.

Coding Week 10: July 30-August 5

• work on getting the PR merged.

Coding Week 11: August 6-August 12

Submit code and evaluations: August 13-August 21 (final evaluation August 19-26)