track backwards incompatible changes
Bug #1406470 reported by
Steve Martinelli
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
High
|
Steve Martinelli |
Bug Description
In the N+1 version, we can remove some of behaviour that we are keeping around for one release cycle.
1) We changed the positional / optional arguments for v2 service creation (identity)
2) We have `project usage list` and `usage list` which perform the same command, we should remove the former.
Changed in python-openstackclient: | |
milestone: | none → m7 |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in python-openstackclient: | |
milestone: | m7 → none |
Changed in python-openstackclient: | |
assignee: | nobody → Steve Martinelli (stevemar) |
milestone: | none → m10 |
Changed in python-openstackclient: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Not sure this is a bug...we could tag reviews with compatibility doc needs and grab them at release time for the release notes and scheduling future follow-up work to remove deprecated bits.