69
edits
Support:Search Implementation: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 4: | Line 4: | ||
All bugs that are needed for SUMO search deployment will be made dependent on this bug. | All bugs that are needed for SUMO search deployment will be made dependent on this bug. | ||
==General Strategy== | |||
*The new search will be deployed in parallel to the old search, so it does not replace the old search but is an add-on. | |||
*The new search will be available once ready at a different URL from the old search | |||
*To phase in the deployment, users will be "chosen" to use the new search randomly. A cookie can be saved with this info to make it less disruptive to users. On the new search results, there will be a message to say that this is a new search that is being tested, and link to go back to the old search (I've seen Google test apps this way). | |||
==Major Targets== | |||
===October 27=== | |||
*Search UI will be ready for review | |||
*Method of deploying search system to be tested | |||
===November 3=== | |||
*Search engine to be ready on support-stage (security by obscurity will apply - you need to know the special url to get to it) | |||
*Initial QA on support-stage to begin | |||
===November 10=== | |||
*Search UI to be finalized | |||
*Search indexing procedure to be finalized | |||
*Search engine to be ready on production (security by obscurity will apply - you need to know the special url to get to it) | |||
*Continued QA on production | |||
===November 17=== | |||
*Testing of different search indexing to begin | |||
===November 24=== | |||
*Documentation of different results of different search indexing parameters done | |||
===December 1=== | |||
*Search is ready for real live users progressive testing | |||
===December 15=== | |||
*Complete cut-over to new search | |||
==Weekly Schedule== | ==Weekly Schedule== | ||
=== | ===October 20-26=== | ||
*Install latest Sphinx on khan | *Install latest Sphinx on khan | ||