Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epf-dev] Iteration C2 assessment and T1 planning - notes

I'll be there. Scott Ambler tells me there are 15-20 people from IBM going.  It would be nice if we could get some of them to promote the practice library.

Ken

On Thu, Jul 31, 2008 at 1:15 AM, Steve Adolph <steve@xxxxxxxxxxxxxxxxx> wrote:
Hello everyone:



Overslept and missed this morning's telecon, little consequence though
sinceI have nothing to report of consequence.



Quick question who is attending Agile next week?



best regards,

Steve



From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Ricardo Balduino
Sent: Wednesday, July 30, 2008 11:01 AM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] Iteration C2 assessment and T1 planning - notes




Here's a summary of the iteration assessment we had today. Please let me
know if I missed any information.
Thanks,

Ricardo.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Iteration C2 Assessment and Iteration T1 Planning


Assessment target

C2 Iteration


Assessment date

7/30/08


Participants

Ricardo Balduino, Felix de Onandia, Bruce MacIsaac, Ken Clyne, and Mark
Dickson.

[Nate Oster, Kim Werner, and Chris Sibbald are on vacation (back on mid
August)
Ana Pereira had a schedule conflict and wasn't able to join.]


Project status

Yellow - we have 40 bugs in new/assigned state




Assessment against objectives

Architecture practice - 4 bugs are unresolved. Two are trivial. Three will
be addressed by Mark and 1 by another contributor.

PM practices - 9 bugs left. Ricardo and Ana will address those bugs, but
extra help is always welcome.

Other practice owners weren't available to report status.

Other concerns and deviations

We need to motivate people to finish an amount of bugs per week on the next
3 weeks otherwise we won't finish all planned work on this release.

Felix will send note asking each content author what is realistic about
finishing their bugs by the release date. If they can't do it, we will have
to find a contingency plan (other volunteers? drop features?). Each person
gives estimate on how much time they need to finish. Each person shows plan
to complete bugs. If not feasible, we can try allocating bugs to other
people.

We should freeze content one week before release. Freeze on 15th and do test
until 17th. From 18th through 20th, we will do fixing and polishing of the
content.

In two weeks all bugzillas should be at least in resolved state.

Nate and Kim are out until 15th, who can take their bugs over? - ask Jim and
Dan about contingency plan. If there isn't one, ask epf-dev for help.

Only 2 practice owners (thanks Mark and Ana) sent list of contributors on
their practices. We need this from everyone so we can pass the Eclipse
Release Review. This material needs to be in place one month before the
release, so we are clearly running short on time.


_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev



Back to the top