Support:Search Implementation: Difference between revisions

Revision as of 04:43, 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 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

October 20-26

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

October 27-November 2

Bug 460208 - Deploy new sumo search engine to support-stage
Bug 460211 - Implement memcache for new sumo search
Implement generic filter by categoriestest cluster

November 3-10

0.7.2 Freeze and push this week

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

Week of November 10

Bug 460214 - Optimize new sumo search results caching
Test different indexing parameters on support-stage

Week of November 17

November 20: 0.7.3 freeze

Performance testing on production

Week of November 24

November 25: 0.7.3 push

@@ Line 51: / Line 51: @@
 *Get in touch with Sphinx to resolve:  Bug 460205 -  Certain characters in some languages cause new sumo search indexing to fail
-===October 27===
+===October 27-November 2===
-*Deploy new search engine to support-stage
+*Bug 460208 -  Deploy new sumo search engine to support-stage
-*Run test indexing on support-stage
+*Bug 460211 -  Implement memcache for new sumo search
-*Do testing of search performance on test cluster
+*Implement generic filter by categoriestest cluster
-===Week of November 3===
+===November 3-10===
-*Implement memcaching for search
+.7.2 Freeze and push this week
-*Test performance with memcache
+*Bug 460213 -  Deploy new sumo search engine to production
+*Bug 460216 -  Set up testing of new sumo search performance on test cluster
 ===Week of November 10===
-*Deploy to production
+*Bug 460214 -  Optimize new sumo search results caching
-*Implement generic filter by categories
 *Test different indexing parameters on support-stage
 ===Week of November 17===
+November 20: 0.7.3 freeze
 *Performance testing on production
-*Implement enhanced memcache logic for new search
 ===Week of November 24===
-*Backup week in case we need to do more testing
+November 25: 0.7.3 push
+===Week of December 1===