Release Instructions

Motivation

When you're using hook_update_N() in the big team there's a high possibility that updating one module may result in numeration conflicts. RI module is developed to avoid that by widening the function name scope.

How?

Module allows you to write the functions with the name format CODE_ri_N, where CODE is your custom prefix, e.g. JIRA ticket abbreviation, and N is any numeric value. Then these functions can be executed via drush like drush updb using the below commands:

1. *drush ri* - execute all release instructions that weren't executed one by one;
2. *drush ri-preview* or *drush rip* - preview ri's function names that weren't yet executed. It makes sense to run that command before applying *drush ri*
3. *drush ri-status FUNCTION STATUS* or *drush ris FUNCTION STATUS* - sets the status of the ri's function, STATUS = 1 or 0 (executed or not).
4. *drush ri-function PATTERN* or *drush rif PATTERN* - executes the functions using the exact name, e.g. test001_ri_1, or the pattern, e.g. test001_ri_*. That command disregards the status of the function.