Difference between revisions of "Horizon/WeeklyBugReport"

Revision as of 13:42, 24 November 2015

Weekly Bug Report (Updated 2015-11-25)

Bugs

• [Medium] [tsufiev] Failure in workflows cause the message to be displayed twice
• [Low] [tsufiev] List of images is not sorted in any useful manner

Weekly Bug Report (Updated 2015-11-18)

Blueprint Patches

• [r1chardj0n3s] Enable PhantomJS for running Selenium tests https://review.openstack.org/#/c/242926
• [tqtran] Adding CREATE action to identity users panel https://review.openstack.org/#/c/222297
• [matt-borland] Split instance details and source in Launch Instance wizard. https://review.openstack.org/#/c/235004/
• [hurgleburgler] Horizon Dropdown now inherits from Bootstrap Theme https://review.openstack.org/#/c/232735/
  • Gated on: https://review.openstack.org/#/c/246549/4

Bugs

• [Critical] [tqtran] Missing documentation for plugins https://bugs.launchpad.net/horizon/+bug/1511593
• [High] project detail link needs policy check https://bugs.launchpad.net/horizon/+bug/1418246
• [High] "Volumes" tab doesn't show up if cinder v1 isn't registered https://bugs.launchpad.net/horizon/+bug/1415712
• [High] [fnordahl] Unable to create subnet from IPv6 subnetpool https://bugs.launchpad.net/horizon/+bug/1498926
• [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
• [??] Horizon navbar-brand should not contain top and bottom padding https://bugs.launchpad.net/horizon/+bug/1518123
  • https://review.openstack.org/#/c/247835/
• [??] Horizon page-header Margin needs to be smaller https://bugs.launchpad.net/horizon/+bug/1518133
  • https://review.openstack.org/#/c/247847/
• [??] Unit tests should not be strict on html contents https://bugs.launchpad.net/horizon/+bug/1517084
  • https://review.openstack.org/#/c/246549

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