Bug 866161 - woodstox-core-4.2.0 is available
Summary: woodstox-core-4.2.0 is available
Keywords:
Status: CLOSED DUPLICATE of bug 976297
Alias: None
Product: Fedora
Classification: Fedora
Component: woodstox-core
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-14 12:10 UTC by Upstream Release Monitoring
Modified: 2016-02-01 01:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-20 12:30:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Upstream Release Monitoring 2012-10-14 12:10:44 UTC 
Latest upstream release: 4.1.4
Current version in Fedora Rawhide: 4.1.2
URL: http://wiki.fasterxml.com/WoodstoxDownload

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Comment 1 Upstream Release Monitoring 2013-02-28 10:16:18 UTC 
Latest upstream release: 4.1.5
Current version in Fedora Rawhide: 4.1.2
URL: http://wiki.fasterxml.com/WoodstoxDownload

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Comment 2 Upstream Release Monitoring 2013-04-16 09:49:29 UTC 
Latest upstream release: 4.2.0
Current version in Fedora Rawhide: 4.1.2
URL: http://wiki.fasterxml.com/WoodstoxDownload

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Comment 3 Mikolaj Izdebski 2013-06-20 12:30:19 UTC 

*** This bug has been marked as a duplicate of bug 976297 ***
Note You need to log in before you can comment on or make changes to this bug.