Current State

Id Summary Applies To Priority Current State Last Edit Waiting For
Item2 edittopic Support multiple extents for storing large files (filesize > bandsize) SMR Enhancement Closed 17 Jan 2015 - 04:55 PratikShah
Item6 edittopic unique inode numbers are not assigned across SMRfs mounts/unmounts SMR Urgent Closed 17 Jan 2015 - 04:54  
Item7 edittopic cleanup flow after flush_to_disk doesn't remove all contents properly SMR Urgent Being Worked On 17 Jan 2015 - 04:53  
Item4 edittopic Test bug SMR Enhancement Closed 25 Oct 2013 - 18:51  
Item3 edittopic Test Bug SMR Enhancement Closed 25 Oct 2013 - 18:51  
Item1 edittopic Test bug report SMR Urgent Closed 25 Oct 2013 - 18:48  
Item5 edittopic Max number of files possible are 2^32 SMR Enhancement Confirmed 24 Oct 2013 - 20:19  
Summary   SMR: 7 Enhancement: 4
Urgent: 3
Being Worked On: 1
Closed: 5
Confirmed: 1
   
  • CurrentState : .*
  • Summary : .*
  • AppliesTo : .*
  • WaitingFor : .*
  • Priority : .*
  • ReportedBy : .*


Documentation for item editing

Current State

  • New - the issue has just been found, and hasn't been analysed yet, or there is new data about an existing issue.
  • Waiting for Feedback - the report was insufficient to analyse the issue, and more feedback is needed from the person named in the "Waiting For" field. Once the reporter has added feedback they should flip the state back to "New". If feedback is not received within 30 days, the issue will be discarded.
  • Confirmed - the issue has been analysed, and the priority has been confirmed (or changed) by a developer. The item can henceforth be classified regarding release blocking status etc. Someone needs to pick it up and fix it.
  • Being Worked On - the issue has been analysed, and is being worked on by the developer named inthe "Waiting For" field.
  • Waiting for Release - the issue reported has been fixed and is queued for release. See the TargetRelease field to see whether it is queued for the next patch, minor, or major release. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why.
  • Closed - the issue has been fixed to the satisfaction of the fixer, and has been through the "Waiting for release" state, and is now released to end users. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why. Note that bugs reported against new code (code that has not been released yet) or Extensions (Plugins etc) may jump straight to "Closed" without going through "Waiting for Release" first.
  • No Action Required - the issue was already fixed, or it's a duplicate, or a RTFM, or could not be reproduced and feedback was never received.

Please make sure there is an entry in the details explaining any state change.


CurrentState option definitions

Name Type ToolTip
New option the issue has just been found, and hasn't been analysed yet, or there is new data about an existing issue.
Waiting for Feedback option the report was insufficient to analyse the issue, and more feedback is needed from the person named in the "Waiting For" field. Once the reporter has added feedback they should flip the state back to "New". If feedback is not received within 30 days, the issue will be discarded.
Confirmed option the issue has been analysed, and the priority has been confirmed (or changed) by a developer. The item can henceforth be classified regarding release blocking status etc. Someone needs to pick it up and fix it.
Being Worked On option the issue has been analysed, and is being worked on by the developer named inthe "Waiting For" field.
Waiting for Release option the issue reported has been fixed and is queued for release. See the TargetRelease field to see whether it is queued for the next patch, minor, or major release. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why.
Closed option the issue has been fixed to the satisfaction of the fixer, and has been through the "Waiting for release" state, and is now released to end users. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why. Note that bugs reported against new code (code that has not been released yet) or Extensions (Plugins etc) may jump straight to "Closed" without going through "Waiting for Release" first.
No Action Required option the issue was already fixed, or it's a duplicate, or a RTFM, or could not be reproduced and feedback was never received.
Topic revision: r1 - 16 Oct 2013, ChuckCranor - This page was cached on 05 Jul 2017 - 18:40.

This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding PDLWiki? Send feedback