Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1060172 - rubygem-shoulda-3.5.0 is available
Summary: rubygem-shoulda-3.5.0 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-shoulda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1115491 1115554
Blocks: 1107062 1107065
TreeView+ depends on / blocked
 
Reported: 2014-01-31 11:09 UTC by Upstream Release Monitoring
Modified: 2014-07-07 12:59 UTC (History)
4 users (show)

Fixed In Version: rubygem-shoulda-3.5.0-1.fc21
Doc Type: Enhancement
Doc Text:
Feature: Reason: Result (if any):
Clone Of:
Environment:
Last Closed: 2014-07-07 12:59:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Upstream Release Monitoring 2014-01-31 11:09:39 UTC 
Latest upstream release: 3.5.0
Current version/release in Fedora Rawhide: 2.11.3-8.fc21
URL: http://rubygems.org/api/v1/gems/shoulda.json

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 Josef Stribny 2014-06-10 08:57:38 UTC 
Hi,

I would really need a shoulda version higher than '3.1' since the 2.x versions seem to be incompatible with Minitest 5 (which we already use in Fedora). Will you please update it? It will also need the shoulda-matchers gem to be packaged.

If not, I already applied for the commit rights, so if you approve me I will submit shoulda-matchers for a review and do the update.
Note You need to log in before you can comment on or make changes to this bug.