Jump to: navigation, search

Difference between revisions of "Horizon/WeeklyBugReport"

m
Line 1: Line 1:
 
== Weekly Bug Report (Updated 2015-11-09) ==
 
== Weekly Bug Report (Updated 2015-11-09) ==
  
=== Blueprint Patches (3) ===
+
=== Blueprint Patches ===
  
 
* [tqtran] Adding CREATE action to identity users panel https://review.openstack.org/#/c/222297
 
* [tqtran] Adding CREATE action to identity users panel https://review.openstack.org/#/c/222297
Line 7: Line 7:
 
* [hurgleburgler] Dropdowns should have a consistent design https://review.openstack.org/#/c/232734
 
* [hurgleburgler] Dropdowns should have a consistent design https://review.openstack.org/#/c/232734
  
=== Bugs (4) ===
+
=== Bugs ===
  
 
* [Critical] [tqtran] Missing documentation for plugins https://bugs.launchpad.net/horizon/+bug/1511593
 
* [Critical] [tqtran] Missing documentation for plugins https://bugs.launchpad.net/horizon/+bug/1511593

Revision as of 15:42, 9 November 2015

Weekly Bug Report (Updated 2015-11-09)

Blueprint Patches

Bugs

About

A short weekly summary of blueprints and bugs that are currently of key importance to Horizon.

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/mitaka-horizon-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