Difference between revisions of "PDE/Retrospective"

From Eclipsepedia

< PDE
Jump to: navigation, search
Line 1: Line 1:
This page will be used to collect comments about PDE and our development process that were noticed during 3.7.  What did we do well?  What could be better?  What should we do next release?
+
Each year the PDE team participates in a retrospective where we look at what areas we have improved in and what areas we need to improve in the next release.  We try to create action items out of these suggestions.
  
== Coding Best Practices ==
+
[PDE/Retrospective/3.7 3.7 Retrospective]
  
* When writing tests, try to keep them stable. Intermittent failures cause headaches.
+
[PDE/Retrospective/3.6 3.6 Retrospective]
* Always keep documentation in mind.  If you see missing doc and don't fix, always file a doc bug.
+
 
+
== Bugzilla ==
+
 
+
* Add proper keywords: '''contributed''' for patches, '''noteworthy''' for big features, '''helpwanted''' for bugs that will only be fixed with contributed patches
+
* When a patch is provided for review by a committer, only commit the patch if the issue is time sensitive and the patch creator has stated you can commit.  In all other cases let the patch contributor commit their own fix.
+
 
+
== General Comments ==
+
 
+
* Meeting minutes were not helpful, whereas the actual meetings were productive.
+

Revision as of 12:47, 6 June 2011

Each year the PDE team participates in a retrospective where we look at what areas we have improved in and what areas we need to improve in the next release. We try to create action items out of these suggestions.

[PDE/Retrospective/3.7 3.7 Retrospective]

[PDE/Retrospective/3.6 3.6 Retrospective]