Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Platform UI/Retrospective/3.5"
(→What worked well) |
(Add my thoughts.) |
||
Line 2: | Line 2: | ||
* I liked that we had no big surprises or dramas during the end game. ''-Boris'' | * I liked that we had no big surprises or dramas during the end game. ''-Boris'' | ||
* I think the new bug triage strategy was a great idea. ''-Eric'' | * I think the new bug triage strategy was a great idea. ''-Eric'' | ||
+ | ** +1. ''-Remy'' | ||
== What didn't work well == | == What didn't work well == | ||
Line 7: | Line 8: | ||
== Ideas for improvement == | == Ideas for improvement == | ||
+ | * I think we still have too many bugs that goes fixed without a unit test. This is not specific to the 3.5 cycle. I will admit that we have a severe "lack of resources" problem on UI. ''-Remy'' | ||
* | * |
Revision as of 23:48, 10 July 2009
What worked well
- I liked that we had no big surprises or dramas during the end game. -Boris
- I think the new bug triage strategy was a great idea. -Eric
- +1. -Remy
What didn't work well
- Unfortunately, some of the performance regressions were discovered very late. We should pay more attention to this earlier in the cycle. -Boris
Ideas for improvement
- I think we still have too many bugs that goes fixed without a unit test. This is not specific to the 3.5 cycle. I will admit that we have a severe "lack of resources" problem on UI. -Remy