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 "Team thoughts on continuous improvement 32"
(→Things we've done well) |
(→Things we'd like to improve on) |
||
| Line 24: | Line 24: | ||
== Things we'd like to improve on == | == Things we'd like to improve on == | ||
| + | |||
| + | fix more old bugs? | ||
| + | track fix rates | ||
| + | |||
| + | junits, more passing builds, less intermittent failures (hard to focus) | ||
| + | |||
| + | performance testing and focus and fixes | ||
| + | |||
| + | [good] welcomed contribution in source editing | ||
| + | [good] improved diversity | ||
| + | |||
| + | could do more explicit verification and closing of fixed bugs | ||
| + | |||
| + | documentation -- long planing from everyone would help doc. teams plan what they need. | ||
| + | |||
| + | keep up better with base prereqs more timely | ||
| + | |||
| + | do we care or measure use of non-API use, discouraged access | ||
| + | |||
| + | build improvements (still needed) | ||
| + | |||
| + | [good] breakout meetings still good .. jee team | ||
| + | |||
| + | ian, keeping up with large bug backlogs ... need a system to not let backlog build up or grow. | ||
| + | |||
| + | |||
Revision as of 14:41, 17 June 2010
Contents
WTP 3.2 Retrospective 06/17/2010
Purpose
Following every release, we have short retrospective to discuss possible ways our project might improve. This starts with a list of things we like and don't like about how the release went, and will evolve into action items with people assigned to be responsible, where appropriate.
Below are initially notes from our 6/17/2010 status meeting. Overtime the notes will be categorized, organized, collapsed, etc., to make correspondence to actions clear.
Things we've done well
Maintained last year's "good" list
JUnit have done better (even if not green as much as they should).
graduation jaxws went smoothly (thanks to shane and daniel)
jsdt good to be "own project", has been getting more help
good at meeting deadlines
ian, good patch responsiveness
bug focus quality area ... less "home work" to do. Kept up.
Things we'd like to improve on
fix more old bugs? track fix rates
junits, more passing builds, less intermittent failures (hard to focus)
performance testing and focus and fixes
[good] welcomed contribution in source editing [good] improved diversity
could do more explicit verification and closing of fixed bugs
documentation -- long planing from everyone would help doc. teams plan what they need.
keep up better with base prereqs more timely
do we care or measure use of non-API use, discouraged access
build improvements (still needed)
[good] breakout meetings still good .. jee team
ian, keeping up with large bug backlogs ... need a system to not let backlog build up or grow.