Support:Search Implementation: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 47: Line 47:
===October 20-26===
===October 20-26===


*Bug 460197 - Create deployment procedure from SVN for search *Nelson looking for help for this*
*Bug 460197 - Create deployment procedure from SVN for search
*Bug 460203 -  Create initial template for new sumo search *Nelson looking for help for this*
*Bug 460203 -  Create initial template for new sumo search
*Get in touch with Sphinx to resolve:  Bug 460205 -  Certain characters in some languages cause new sumo search indexing to fail
*Get in touch with Sphinx to resolve:  Bug 460205 -  Certain characters in some languages cause new sumo search indexing to fail
* Define new sumo search indexing trigger method


===October 27-November 2===
===October 27-November 2===


*Bug 460208 -  Deploy new sumo search engine to support-stage  
*Bug 460208 -  Deploy new sumo search engine to support-stage
*Bug 460211 -  Implement memcache for new sumo search
*Bug 460211 -  Implement memcache for new sumo search '''unassigned'''
*Implement generic filter by categoriestest cluster
*Bug 460219 -  Ensure category and other filters for new sumo search working
*Bug 460220 -  Integrate new sumo search admin
*Bug 460221 -  Define new sumo search indexing trigger method


===November 3-10===
===November 3-9===


0.7.2 Freeze and push this week
0.7.2 Freeze and push this week


*Bug 460213 -  Deploy new sumo search engine to production
*Bug 460213 -  Deploy new sumo search engine to production '''unassigned'''
*Bug 460216 -  Set up testing of new sumo search performance on test cluster
*Bug 460216 -  Set up testing of new sumo search performance on test cluster '''unassigned'''


===Week of November 10===
===November 10-16===


*Bug 460214 -  Optimize new sumo search results caching
*Bug 460214 -  Optimize new sumo search results caching
*Test different indexing parameters on support-stage
*Bug 460223 -  Test and define search indexing cycle/procedure


===Week of November 17===
===November 17-24===


November 20: 0.7.3 freeze  
November 20: 0.7.3 freeze  
 
*Bug 460224 -  Test different search indexing weights
*Performance testing on production
Refinements


===Week of November 24===
===Week of November 24===


November 25: 0.7.3 push
November 25: 0.7.3 push
Refinements


===Week of December 1===
===Week of December 1===
Refinements
=== Week of December 8===
0.8 freeze

Revision as of 05:23, 16 October 2008

The implementation for new SUMO search will run from October 20 to November 30.

The main bug: bug 405028

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 tested and documented

November 3

  • Unoptimized 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
  • Unoptimized 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

October 20-26

  • Bug 460197 - Create deployment procedure from SVN for search
  • Bug 460203 - Create initial template for new sumo search
  • Get in touch with Sphinx to resolve: Bug 460205 - Certain characters in some languages cause new sumo search indexing to fail
  • Define new sumo search indexing trigger method

October 27-November 2

  • Bug 460208 - Deploy new sumo search engine to support-stage
  • Bug 460211 - Implement memcache for new sumo search unassigned
  • Bug 460219 - Ensure category and other filters for new sumo search working
  • Bug 460220 - Integrate new sumo search admin
  • Bug 460221 - Define new sumo search indexing trigger method

November 3-9

0.7.2 Freeze and push this week

  • Bug 460213 - Deploy new sumo search engine to production unassigned
  • Bug 460216 - Set up testing of new sumo search performance on test cluster unassigned

November 10-16

  • Bug 460214 - Optimize new sumo search results caching
  • Bug 460223 - Test and define search indexing cycle/procedure

November 17-24

November 20: 0.7.3 freeze

  • Bug 460224 - Test different search indexing weights

Refinements

Week of November 24

November 25: 0.7.3 push

Refinements

Week of December 1

Refinements

Week of December 8

0.8 freeze