Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691872 - liquibase-2019-02-14_Sprint_5.8_Ver_5.8.5731 is available
Summary: liquibase-2019-02-14_Sprint_5.8_Ver_5.8.5731 is available
Alias: None
Product: Fedora
Classification: Fedora
Component: liquibase
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Devan Goodwin
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-22 17:08 UTC by Upstream Release Monitoring
Modified: 2019-03-27 14:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2019-03-27 14:41:33 UTC

Attachments (Terms of Use)

Description Upstream Release Monitoring 2019-03-22 17:08:20 UTC
Latest upstream release: 2019-02-14_Sprint_5.8_Ver_5.8.5731
Current version/release in rawhide: 3.6.1-3.fc30

Please consult the package updates policy before you issue an update to a stable branch:

More information about the service that created this bug can be found at:

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from anitya:

Comment 1 Alex Wood 2019-03-27 14:41:33 UTC
Latest release is 3.6.3.  Git Hub is reporting 2019-02-14_Sprint_5.8_Ver_5.8.5731 as a release, but it's not marked as being the "latest release" and the name of the tag is odd.  I'm not sure what this tag is, but I'm going to consider this bug a false positive from Upstream Release Monitoring.

Note You need to log in before you can comment on or make changes to this bug.