Difference between revisions of "Team thoughts on continuous improvement 31"

From Eclipsepedia

Jump to: navigation, search
(possible actions)
(possible actions)
Line 63: Line 63:
 
::someone (dw?) still needs to re-do our build scripts?
 
::someone (dw?) still needs to re-do our build scripts?
  
=== Communication, Documentation ===
+
=== Communication, Documentation ===
  
 
Lack of dependent project communication, such as emf or platform, both if and when "breaking" changes coming and once we learn of it, seems there's no central place to learn of all "breaking changes".  
 
Lack of dependent project communication, such as emf or platform, both if and when "breaking" changes coming and once we learn of it, seems there's no central place to learn of all "breaking changes".  
  
:: dw to work with Planning Council on common area for "migration issues" (similar to our 'new help for old friends' pages).  
+
::dw to work with Planning Council on common area for "migration issues" (similar to our 'new help for old friends' pages).
  
Hard for newcomers (even adopters) to get "acquainted" or integrated with WTP policies, practice, and rhythms so testing isn't done early enough and communication is awkward, hard and takes too long to get worked out. [The break-out meetings such as for JEE have helped.]
+
Hard for newcomers (even adopters) to get "acquainted" or integrated with WTP policies, practice, and rhythms so testing isn't done early enough and communication is awkward, hard and takes too long to get worked out. [The break-out meetings such as for JEE have helped.]  
  
:: Documents to improve: hotbug process, "How to contribute to WTP", "How to Ask Questions", "How to submit a bug", ...  
+
:Improve documentation: hotbug process, "How to contribute to WTP", "How to Ask Questions", "How to submit a bug", ...  
 +
:Improve home web page
  
<br>
+
::define/describe levels of particpation:
<br>
+
  
[[Category:WTP Continuous Improvement| ]]
+
:::use-only
 +
:::download
 +
:::bugs
 +
:::contribute a patch
 +
:::adopters - early tests
 +
 
 +
<br> <br>
 +
 
 +
[[Category:WTP_Continuous_Improvement|WTP_Continuous_Improvement]]

Revision as of 22:39, 16 July 2009

Contents

WTP 3.1 Debriefing 07/09/2009

Purpose

Following our WTP 3.1 release, we had short post mortem 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 the notes from our 7/9/2009 status meeting.

Things we've done well

Policy and practice of firm deadline for weekly I-build with same-day declare.

Regular, consistent weekly (Thursday) is build good, even if actual delivery following Tuesday.

Some long standing performance bugs finally addressed (in XML Editing and related).

Plans (XML format and bugzilla entries) with dynamic, iterative updates worked well.

Team discussion "broken out" to their own regular meetings, so they don't overwhelm WTP status call with detail (that only a few on call are interested in).

Dates on Google calendar helps keep all coordinated by having dates in a central spot.

Frequent (weekly) but short status calls.

Things we'd like to improve on

Build, process, practice

Too many intermittent junit failures: especially in that there are too many long periods build failures. Failures (even compile errors) begin to be ignored since failures so common.

Builds take too long: especially in that it takes a long time to get notified if problem or not after checking in code.

break up build into smaller pieces
make tests more reproducible on build machine (suite by suite)
build break leader board?
Insist each build is green -- or fix within 24 hours.
provide better summary of failures ... Summary at top of page
Mail notices: better document severity, repeatedness, exact issues
improve versioning page so errors easier to see.
in general, too much noise ... change versioning errors back to warnings ... make blocking for milestones
remove intermittant failure JUnits
log junit failures in database (for more history)
use API tools

Lots of code checked in with no junit test (both new function and bug fixes).

project leads should instill the attitude and practice
are there tools or training we can give ourselves to make it easier?

Lack performance suite or benchmarks.

someone (dw?) still needs to re-do our build scripts?

Communication, Documentation

Lack of dependent project communication, such as emf or platform, both if and when "breaking" changes coming and once we learn of it, seems there's no central place to learn of all "breaking changes".

dw to work with Planning Council on common area for "migration issues" (similar to our 'new help for old friends' pages).

Hard for newcomers (even adopters) to get "acquainted" or integrated with WTP policies, practice, and rhythms so testing isn't done early enough and communication is awkward, hard and takes too long to get worked out. [The break-out meetings such as for JEE have helped.]

Improve documentation: hotbug process, "How to contribute to WTP", "How to Ask Questions", "How to submit a bug", ...
Improve home web page
define/describe levels of particpation:
use-only
download
bugs
contribute a patch
adopters - early tests