This is a guide for core committers of Evergreen.

1. Confirm that there are no unintended side effects to the upgrade script (data loss, performance issues, etc.)
2. Figure out the next number in the upgrade script sequence.
3. Announce on IRC that you are "claiming" that number.
4. Edit the upgrade script to make sure there is an uncommented evergreen.upgrade_deps_block_check line with the upgrade script number.
5. Change the file name of the upgrade script to start with the number.
6. In 002.schema.config.sql, update the config.upgrade_log value to match the upgrade script number. Update the comment at the end to include the nicknames of the people involved in the patch (this is around line 95).
7. Commit the upgrade script and 002.schema.config.sql changes, using a commit message like "Stamp upgrade script"

If backporting the upgrade script to a release branch, use the same sequence number as you did in the main branch. For example, if you commit an upgrade script number 1234 to main, it should also be numbered 1234 in release branches.