Answers.Body: <p>If you're targeting the <code>4.6</code> branch, then put the upgrade script in the latest <code>4.6.X.mysql.tpl</code>. If you're targeting the <code>master</code> branch, then use <code>4.7.alpha1.mysql.tpl</code>.</p>
  
  <p>As a rule of thumb, we try to minimize schema changes in stable release branches (e.g. 4.6.x) and instead put them in <code>master</code>. But that's not absolute.</p>
  
  <p>The difference between a bugfix and a new feature is a bit academic. When a user installs vX.Y.Z., the upgrader needs to apply all schema changes needed to match vX.Y.Z.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-09T08:06:32.457Z
Answers.LastActivityDate: 2015-08-09T08:06:32.457Z
Answers.UserDisplayName: Tim Otten
Body: <p>I am following instructions here: <a href="https://github.com/civicrm/civicrm-buildkit/blob/master/doc/daily-coding.md#upgrade-tests" rel="nofollow">https://github.com/civicrm/civicrm-buildkit/blob/master/doc/daily-coding.md#upgrade-tests</a> to add and test a schema update - the upgrade is to add 2 columns to the core event table. A (perhaps stupid) question, do I update the latest version of the versioned (e.g 4.6.*alpha.sql, 4.6.*beta) files in ..Incremental/sql? Since this is not a fix/addition to a particular version but part of brand-new functionality, is that a good assumption?</p>
  
Tags: <upgrade><civicrm-buildkit>
Title: How to modify/test Upgrade/Incremental/sql..sql script?
ThreadText: # How to modify/test Upgrade/Incremental/sql..sql script?
  
  (Asked by: username_0 on 2015-08-07)
  
  I am following instructions here: <https://github.com/civicrm/civicrm-buildkit/blob/master/doc/daily-coding.md#upgrade-tests> to add and test a schema update - the upgrade is to add 2 columns to the core event table. A (perhaps stupid) question, do I update the latest version of the versioned (e.g 4.6.\*alpha.sql, 4.6.\*beta) files in ..Incremental/sql? Since this is not a fix/addition to a particular version but part of brand-new functionality, is that a good assumption?
  
  **Tags:** upgrade, civicrm-buildkit
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-08-09. Score: 2
  
  If you're targeting the `4.6` branch, then put the upgrade script in the latest `4.6.X.mysql.tpl`. If you're targeting the `master` branch, then use `4.7.alpha1.mysql.tpl`.
  
  As a rule of thumb, we try to minimize schema changes in stable release branches (e.g. 4.6.x) and instead put them in `master`. But that's not absolute.
  
  The difference between a bugfix and a new feature is a bit academic. When a user installs vX.Y.Z., the upgrader needs to apply all schema changes needed to match vX.Y.Z.
  
  
  ---
  
  