[SENTRY-2398] Support multiple target versions on single source versions during schema upgrades

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: Sentry
• Assignee: Sergio Peña
• Reporter: Sergio Peña
• Created: 11/Sep/18 17:06
• Updated: 13/Sep/18 16:39
• Resolved: 13/Sep/18 16:30

Description

Currently, the SentrySchemaTool allows only upgrade versions that are in the order found in the upgrade.order.<db> files. However, having multiple direct target versions per source version is desired when dealing with complex scenarios where the upgrade path is not in the order of the file.

For example:
   1.8.0 -> 1.9.0
   1.8.0 -> 2.0.0
   1.9.0 -> 2.1.0
   2.0.0 -> 2.1.0

 

The above scenario mentions that 1.8.0 is allowed to be upgraded to 1.9.0 or 2.0.0, but 1.9.0 cannot upgrade to 2.0.0. Also, the 1.8.0 -> 2.0.0 was created before a 1.9.0 version is released.

Issue Links

• links to: Review Board