Difference between revisions of "Bugtracking for Developer"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (additional category)
(Duties for Developers)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Quality Assurance]]
+
[[Category:Policy]]
[[Category:Development]]
+
  
 
== Duties for Developers ==
 
== Duties for Developers ==
  
* review patch issues (give feedback, approval, integrate), see [http://eis.services.openoffice.org/patchreport/irt_index.html Initial Response Time] (IRT) and [http://eis.services.openoffice.org/patchreport/iit_index.html Issue Inactivity Time] (IIT)
+
* review patch issues (give feedback, approval, integrate), see <s>[http://eis.services.openoffice.org/patchreport/irt_index.html Initial Response Time]</s> <font color="red">deprecated</font> (IRT) and <s>[http://eis.services.openoffice.org/patchreport/iit_index.html Issue Inactivity Time]</s> <font color="red">deprecated</font>(IIT)
  
 
* issues with regression keyword set have highest priority, either explain why they are "regressions by design" and reset the regression keyword or issues need to be fixed.
 
* issues with regression keyword set have highest priority, either explain why they are "regressions by design" and reset the regression keyword or issues need to be fixed.
Line 14: Line 13:
 
* work on issues scheduled for "integration asap" (e.g. OOo 2.x)
 
* work on issues scheduled for "integration asap" (e.g. OOo 2.x)
  
* reconsider priorities of your own or your boss (or votes, other feedback) and adjust the target.
+
* reconsider priorities of your own or your boss (or [[votes]], other feedback) and adjust the target.
  
Note: Unconfirmed Issues will first reviewed by the QA Team, it is not expected that developer work on unconfirmed issues. Exception: Code Patches of issue has been passed through QA to Developer.
+
{{Note| Unconfirmed Issues will first reviewed by the QA Team, it is not expected that developer work on unconfirmed issues. Exception: Code Patches of issue has been passed through QA to Developer.}}

Latest revision as of 13:06, 10 August 2022


Duties for Developers

  • issues with regression keyword set have highest priority, either explain why they are "regressions by design" and reset the regression keyword or issues need to be fixed.
  • review new issues (defects) and assign an appropiate target to them (at least once a week)
  • work on issues (defect or features) for next release (e.g. OOo 2.0.4) according issues priority
  • work on issues scheduled for "integration asap" (e.g. OOo 2.x)
  • reconsider priorities of your own or your boss (or votes, other feedback) and adjust the target.
Documentation note.png Unconfirmed Issues will first reviewed by the QA Team, it is not expected that developer work on unconfirmed issues. Exception: Code Patches of issue has been passed through QA to Developer.
Personal tools