raising the minimum version of a requirement in one project should not require raising it everywhere

Bug #1621148 reported by Doug Hellmann
This bug report is a duplicate of:  Bug #1719009: per project requirements. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Global Requirements
Confirmed
High
Unassigned

Bug Description

At the Newton summit we discussed a way to allow overlapping requirements that don't match exactly. We should prioritize that work.

https://etherpad.openstack.org/p/newton-global-requirements

Revision history for this message
Tony Breeds (o-tony) wrote :

This is a team goal for Ocata

Changed in openstack-requirements:
importance: Undecided → High
status: New → Confirmed
tags: added: divergent-requirements lower-bounds-testing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.