Bug 1207994

Summary:	RFE/TECH DEBT: Upgrade to Liquibase 3.3
Product:	[Retired] Zanata	Reporter:	Sean Flanigan <sflaniga>
Component:	DatabaseChange, Maintainability	Assignee:	Sean Flanigan <sflaniga>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Damian Jansen <djansen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7	CC:	dchen, djansen, zanata-bugs
Target Milestone:	---
Target Release:	3.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.7.0-SNAPSHOT	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-22 02:20:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1207980

Description Sean Flanigan 2015-04-01 07:33:05 UTC

Description of problem:
We should upgrade from Liquibase 3.0.7 to 3.3.2.

Additional info:

Liquibase changelogs are here: http://blog.liquibase.org/category/announcement (From a quick read, I can't see any problems which should affect us)

Previous updates were covered in bug 813165 and bug 1036435.

Comment 1 Sean Flanigan 2015-04-07 02:37:59 UTC

Pull request: https://github.com/zanata/zanata-server/pull/761

Comment 2 Sean Flanigan 2015-04-07 05:58:58 UTC

We need to test that existing databases are migrated without throwing any exceptions (like "change sets check sum 'abc' is now: 'xyz'").

Comment 4 Sean Flanigan 2015-05-15 07:31:45 UTC

See also https://liquibase.jira.com/browse/CORE-2024 and https://github.com/zanata/zanata-server/pull/811

Comment 5 Damian Jansen 2015-05-19 01:05:36 UTC

Verified (master) at f754844e6f68107f09b2b655dcdd429f78dc2167