[Xapian-tickets] [Xapian] #566: Merge learning to rank branch

[Xapian]

#566: Merge learning to rank branch
-------------------------+--------------------------------------------------
 Reporter:  richard      |       Owner:  parth
     Type:  enhancement  |      Status:  new  
 Priority:  normal       |   Milestone:  1.3.2
Component:  Library API  |     Version:       
 Severity:  normal       |    Keywords:       
Blockedby:               |    Platform:  All  
 Blocking:               |  
-------------------------+--------------------------------------------------
Changes (by olly):

  * component:  Other => Library API


Old description:

> We should work on merging the letor branch to trunk, to ensure it doesn't
> bitrot and get lost.
>
> To get an overview of changes on the letor branch, see
> https://github.com/xapian/xapian/compare/master...svn%2Fgsoc2011-parth
>
> Several things need to be done.  Initially, by parth:
>
>  - add the letor/dir_contents file, so the build system works.
>
>  - remove letor/svm.h; the installed svm.h should be used instead.
>
>  - add the formulae to the docs/letor.rst file (in latex form, we can
> worry about making them display nicely later).
>
>  - add a description of which versions of libsvm should work to the
> docs/letor.rst file.
>
>  - remove the include of letor.h from xapian.h, and add a comment to the
> top of letor.h to indicate that it is not part of the official stable
> API.
>
> At this point, parth can submit his code to google, and the gsoc project
> is finished.
>
> Then, by olly or me:
>
>  - merge recent changes in trunk to the branch
>
>  - add detection of libsvm.h to configure.ac
>
>  - make the build skip letor if svm.h isn't available
>
>  - anything else required to merge the branch to trunk
>
>  - check that at least one buildbot is building the letor code.
>
> I've marked this as milestone 1.3.0 so it doesn't get forgotten, but
> consider that a soft milestone.

New description:

 We should work on merging the letor branch to trunk, to ensure it doesn't
 bitrot and get lost.

 To get an overview of changes on the letor branch, see
 https://github.com/xapian/xapian/compare/master...svn%2Fgsoc2011-parth

 Several things need to be done.  Initially, by parth:

  - '''Done:''' ''add the letor/dir_contents file, so the build system
 works.''

  - '''Done:''' ''remove letor/svm.h; the installed svm.h should be used
 instead.''

  - '''Done:''' ''add the formulae to the docs/letor.rst file (in latex
 form, we can worry about making them display nicely later).''

  - '''Done:''' ''add a description of which versions of libsvm should work
 to the docs/letor.rst file.''

  - '''Done:''' ''remove the include of letor.h from xapian.h, and add a
 comment to the top of letor.h to indicate that it is not part of the
 official stable API.''

 At this point, parth can submit his code to google, and the gsoc project
 is finished.

 Then, by olly or me:

  - merge recent changes in trunk to the branch

  - add detection of libsvm.h to configure.ac

  - make the build skip letor if svm.h isn't available

  - make the code conform to the coding conventions we use in the rest of
 the code (partly done)

  - add automated tests (parth will try to do this)

  - anything else required to merge the branch to trunk

  - check that at least one buildbot is building the letor code.

 I've marked this as milestone 1.3.0 so it doesn't get forgotten, but
 consider that a soft milestone.

--

Comment:

 I've updated the description to mark what has been done, and to note a few
 more things to do.

 I wonder if it would make more sense to make this a separate top-level
 module (e.g. xapian-letor), rather than an optionally built part of
 xapian-core?

-- 
Ticket URL: <http://trac.xapian.org/ticket/566#comment:6>
Xapian <http://xapian.org/>
Xapian