Difference between revisions of "Horizon/WeeklyBugReport"
< Horizon
m |
Timur Sufiev (talk | contribs) (→Bugs) |
||
| (55 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == Weekly Bug Report (Updated | + | == Weekly Bug Report (Updated 2016-05-18) == |
=== Blueprint Patches === | === Blueprint Patches === | ||
| − | * [ | + | * [r1chardj0n3s] Additional functionality improvements for Swift UI - https://blueprints.launchpad.net/horizon/+spec/swift-ui-functionality |
| − | * [ | + | ** https://review.openstack.org/313243 |
| − | * | + | * [tsufiev] Streamline glance images upload via Horizon https://blueprints.launchpad.net/horizon/+spec/horizon-glance-large-image-upload |
| + | ** https://review.openstack.org/230434/ | ||
=== Bugs === | === Bugs === | ||
| − | * [ | + | * [High] Building Dashboard Tutorial test fails - https://bugs.launchpad.net/horizon/+bug/1451960 |
| − | * | + | ** https://review.openstack.org/181459 |
| − | * [ | + | * [Medium] [ducttape] admin system info page shows useless data, hides useful data - https://bugs.launchpad.net/horizon/+bug/1497448 |
| − | * | + | ** https://review.openstack.org/225334 |
| − | * [Medium] [ | + | * [Medium] [tsufiev] UpdateProjectQuotas doesn't pay attention on disabled_quotas - https://bugs.launchpad.net/horizon/+bug/1286099 |
| + | ** https://review.openstack.org/215277 | ||
=== About === | === About === | ||
| − | A short weekly summary of blueprints and bugs that are currently of key importance to Horizon. | + | A short weekly summary of blueprints and bugs that are currently of key importance to Horizon. This is to help those short on review time scope their time effectively, or give newcomers a quick list of priority patches to look at. |
Criteria: | Criteria: | ||
* Bugs should have submitted patches, or active discussion around the solution. This report is for showing solutions, not discussing validity of new bug reports. The patches should also be in a relatively good state (i.e. passing Jenkins, not stale) | * Bugs should have submitted patches, or active discussion around the solution. This report is for showing solutions, not discussing validity of new bug reports. The patches should also be in a relatively good state (i.e. passing Jenkins, not stale) | ||
| − | * Patches should be based around the current cycles priorities (https://etherpad.openstack.org/p/ | + | * Patches should be based around the current cycles priorities (https://etherpad.openstack.org/p/horizon-newton-priorities) |
* For blueprints, list a specific patch rather than the entire blueprint. It is unlikely an entire feature will be merged in a week, but focusing on a single patch is reasonable | * For blueprints, list a specific patch rather than the entire blueprint. It is unlikely an entire feature will be merged in a week, but focusing on a single patch is reasonable | ||
* Add IRC handles if possible, to aid communication | * Add IRC handles if possible, to aid communication | ||
Latest revision as of 13:58, 24 May 2016
Weekly Bug Report (Updated 2016-05-18)
Blueprint Patches
- [r1chardj0n3s] Additional functionality improvements for Swift UI - https://blueprints.launchpad.net/horizon/+spec/swift-ui-functionality
- [tsufiev] Streamline glance images upload via Horizon https://blueprints.launchpad.net/horizon/+spec/horizon-glance-large-image-upload
Bugs
- [High] Building Dashboard Tutorial test fails - https://bugs.launchpad.net/horizon/+bug/1451960
- [Medium] [ducttape] admin system info page shows useless data, hides useful data - https://bugs.launchpad.net/horizon/+bug/1497448
- [Medium] [tsufiev] UpdateProjectQuotas doesn't pay attention on disabled_quotas - https://bugs.launchpad.net/horizon/+bug/1286099
About
A short weekly summary of blueprints and bugs that are currently of key importance to Horizon. This is to help those short on review time scope their time effectively, or give newcomers a quick list of priority patches to look at.
Criteria:
- Bugs should have submitted patches, or active discussion around the solution. This report is for showing solutions, not discussing validity of new bug reports. The patches should also be in a relatively good state (i.e. passing Jenkins, not stale)
- Patches should be based around the current cycles priorities (https://etherpad.openstack.org/p/horizon-newton-priorities)
- For blueprints, list a specific patch rather than the entire blueprint. It is unlikely an entire feature will be merged in a week, but focusing on a single patch is reasonable
- Add IRC handles if possible, to aid communication
