User Tools

Site Tools


dev:committing

This is an old revision of the document!


Guide to committing

This is a guide for core committers of Evergreen.

Committing patches with database upgrade scripts

  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.

  1. Commit the upgrade script and 002.schema.config.sql changes, using a commit message like "Stamp upgrade script"
dev/committing.1699548416.txt.gz · Last modified: 2023/11/09 11:46 by tmccanna

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.