R1 2022 Lotus - Release - 4 Mar 2022 (FOLREL-501)

[LIQUTIL-12] Release v1.3.0 (Lotus) Created: 26/Dec/21  Updated: 09/Dec/22  Resolved: 01/Feb/22

Status: Closed
Project: liquibase-util
Components: None
Affects versions: None
Fix versions: 1.3.0
Parent: R1 2022 Lotus - Release - 4 Mar 2022

Type: Task Priority: P3
Reporter: Kateryna Senchenko Assignee: Kateryna Senchenko
Resolution: Done Votes: 0
Labels: data-import, epam-folijet
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by LIQUTIL-13 Update liquibase lib to v4.7.X (Lotus) Closed
Defines
defines UXPROD-3211 NFR: Lotus R1 2022 Module releases, R... Closed
Gantt End to Start
has to be done before MODSOURCE-450 Increase folio-liquibase-util to v1.3... Closed
Relates
relates to MODPUBSUB-223 Update folio-liquibase-util to v1.3.0... Closed
Sprint: Folijet Sprint 132
Story Points: 0.5
Development Team: Folijet
Release: Lotus R1 2022
Epic Link: R1 2022 Lotus - Release - 4 Mar 2022
Front-End Confidence factor: High

 Description   
  • Release version 1.3.0 (see guide)
  • Check artifacts on Nexus


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 01/Feb/22 ]

Per Ruslan Lavrov
The newly appeared issue related to liquibase (3-rd party library)
is also relevant for Kiwi and Juniper versions of mod-source-record-storage and mod-pubsub modules. It can be fixed by updating the liquibase version in our folio-liquibase-util library
and then by updating folio-liquibase-util library dependency in the modules. Could you please advise should we create tickets for kiwi fix or should approval be requested at first? Thank you!

I'm checking with Mark Veksler on how to proceed. If HF for Kiwi and Juniper, also add follow-up tasks to do manual smoke tests in each Bugfest env.

Comment by Kateryna Senchenko [ 02/Feb/22 ]

Hi Ann-Marie Breaux, looks like the liquibase folks fixed the problem with their lib on their side, the issue must be resolved now without the dependency upgrade. At least, at the moment it looks unnecessary for Juniper. We might still want to release the fix for Kiwi, just to make sure we don't run into this issue again (we faced the same troubles a couple of days ago, then it was fixed, then it broke again)

Comment by Ann-Marie Breaux (Inactive) [ 02/Feb/22 ]

Hi Kateryna Senchenko and cc: Ruslan Lavrov I'll leave it to your discretion. If only Kiwi, that's definitely better than Kiwi+Juniper

Generated at Thu Feb 08 22:13:27 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.