Guidelines for the testing of Level 3 Code for new production releases
During the month before the production release is cut:

• All proposed changes to L3 tools/filters, in particular changes to trigger list parameters, should be announced in an L3 algorithms meeting and summarized in a web page.
  Here is an example for p13.
• All relevant changes to the L3 terms in the trigger database should be made.
• Full testing using Trigsim, based on a trigger list extracted from the trigger database should be performed.