Jump to: navigation, search

Difference between revisions of "Horizon/WeeklyBugReport"

(Blueprint Patches)
(Bugs)
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Weekly Bug Report (Updated 2016-01-28) ==
+
== Weekly Bug Report (Updated 2016-05-18) ==
  
 
=== Blueprint Patches ===
 
=== Blueprint Patches ===
  
* [hurgleburgler] Horizon Checkboxes are now themeable https://review.openstack.org/#/c/252161/
+
* [r1chardj0n3s] Additional functionality improvements for Swift UI - https://blueprints.launchpad.net/horizon/+spec/swift-ui-functionality
* [tsufiev] Increase the coverage of Horizon integration tests
+
** https://review.openstack.org/313243
** https://review.openstack.org/#/c/168935/
+
* [tsufiev] Streamline glance images upload via Horizon https://blueprints.launchpad.net/horizon/+spec/horizon-glance-large-image-upload
** https://review.openstack.org/#/c/268039/
+
** https://review.openstack.org/230434/
  
 
=== Bugs ===
 
=== Bugs ===
  
* [High] [tsufiev] Some Jenkins nodes fail create_instance integration test due to missing network https://bugs.launchpad.net/horizon/+bug/1542211
+
* [High] Building Dashboard Tutorial test fails - https://bugs.launchpad.net/horizon/+bug/1451960
** Patch: https://review.openstack.org/#/c/276678/
+
** https://review.openstack.org/181459
* [Low] [tsufiev] Integration tests @tables.bind_row_action() is too picky about buttons layout https://bugs.launchpad.net/horizon/+bug/1537526
+
* [Medium] [ducttape] admin system info page shows useless data, hides useful data - https://bugs.launchpad.net/horizon/+bug/1497448
** Patch: https://review.openstack.org/271805
+
** https://review.openstack.org/225334
* [Low] Launch instance from Volumes Page opens LEGACY launch instance, even if LEGACY is set to False in local_settings https://bugs.launchpad.net/horizon/+bug/1491645
+
* [Medium] [tsufiev] UpdateProjectQuotas doesn't pay attention on disabled_quotas - https://bugs.launchpad.net/horizon/+bug/1286099
** Patch: https://review.openstack.org/#/c/219925/
+
** https://review.openstack.org/215277
  
 
=== About ===
 
=== About ===
Line 23: Line 23:
 
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/mitaka-horizon-priorities)
+
* 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

Bugs

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