Bug days: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
(New page: Periodically we will have "bug & patch" weekends where developers work to reduce the number of open bugs in the bugzilla and push patches upstream when they are suitable for inclusion....)
 
No edit summary
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
Periodically we will have "bug & patch" weekends where developers work to reduce the number of open bugs in the bugzilla and [[push patches upstream]] when they are suitable for inclusion.  "bug & patch" weekends can have a motto or area of focus and can extend to other housekeeping chores for OpenEmbedded that lend themselves to collaborative sprints.
Bug days have not happened for a while however the concept remains valid and as a project, we do hope to hold them again.
 
The general intent of such days would be to have a block of time where developers get together online and work on addressing specific topics such as:
* reducing the number of open bugs in the bugzilla by fixing bugs and triaging stale bugs
* reviewing and handling unmerged patches
* working though the patches we have against software and submitting suitable code upstream ([[push patches upstream]])
 


[[Category:Policy]]
[[Category:Policy]]

Latest revision as of 10:25, 7 November 2012

Bug days have not happened for a while however the concept remains valid and as a project, we do hope to hold them again.

The general intent of such days would be to have a block of time where developers get together online and work on addressing specific topics such as:

  • reducing the number of open bugs in the bugzilla by fixing bugs and triaging stale bugs
  • reviewing and handling unmerged patches
  • working though the patches we have against software and submitting suitable code upstream (push patches upstream)