Jump to: navigation, search

Difference between revisions of "Horizon/WeeklyBugReport"

m
m
Line 27: Line 27:
 
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

Revision as of 07:46, 4 May 2016

Weekly Bug Report (Updated 2016-05-04)

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