Project Timeline: April 4 – May 4: Will work on

1. Integrating the solution I have developed for Ticket #733.
2. Discussion on Ticket #734
3. Writing Unit tests.

This will be the most crucial time of my semester and I will have to be finishing my thesis work so I might not be able to spend much time on contributing to Xapian as I would like to.

May 5 – May 29: Community Bonding Period: Will work on

1. Writing Unit tests.
2. Integrating the solution I have developed for Ticket #733 if not already done.
3. Discussing the datasets to be used for Testing and Performance.
4. If need be a little discussion on integrating rankers and scorers from vhasu’s work.
5. Discussing Stretch Goals.

May 30 - June 12: Will work on

1. Integrating the solution I have developed for Ticket #733 if not already done.
2. Updating existing documentation.
3. Writing Unit Tests for Feature and FeatureList.

June 13 - June 26: Will work on

1. Ticket #734⟶Returning MSet instead of sorted docids.
2. Updating existing documentation.

June 27 - July 23: Writing automated tests for testing

1. Rankers and Scorers.
2. Letor API.
3. Fixing any bugs that are detected while testing.

June 24 - July 31:

1. Running lcov to identify if more tests are needed.
2. Update the documentation to add examples on how to use letor api or any new functionality added

August 1 - August 14:

1. Integrate ListMLE, ERR and if possible Adarank to get the code to build cleanly without any warnings.
2. Write unit tests for each new feature introduced as and when they are introduced.
3. Updating documentation for each new feature as and when they are introduced.

August 15 - August 21:

1. Testing Performance i.e. precision and accuracy with standard datasets.

August 21 - August 31:

1. Discuss outline the future of Letor and if any further changes are needed.

September 1st: Final Evaluation