[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [epf-dev] Conference Call for OpenUP/Basic package owners tomorrow
|
I will unfortunately not be able to join due to a conflict,
but here's the stuff for PM...
Work Items Left: 32 - Major: 26, Normal: 3, Enhance:
3
New Items Created Last Week: 30
Items Fixed Last Week: 0
Items for Next Week: 137120, 146446, 146445,
146503
Unassigned Items: 31 - need to send out a call to action
and get some people to volunteer
Issues Preventing Progress: Laws of Physics and the
Integrity of the Time-Space Continuum
Something I'm sure others have considered, is that it would
seem that we should be able to get most of this info right out of Bugzilla
automatically with reports. Is someone interested in seeing how well this might
work?
Also, who is responsible for items that aren't attributable
to specific packages/disciplines (such as general items like 146449, 146450,
& 146451 to name a few)?
I've also attached a Process Component Completeness
Guideline that we've used to help describe how done certain things need to be at
throughout the lifecycle of a process component. This isn't exactly aligned with
the UMA metamodel, but hopefully it's close enough to get the idea. I'd be
interested to know if people thought that this might be useful in help guiding
us through R1.0.
Let me know how it goes!
Chris ~:|
Hi, I suggest that each Package / Disicpline owner reports
on a) How many work items are
left? b) How many new work items were
created last week? c) Which work items
were fixed last week? d) Which work
items do you plan to fix next week? e)
How many unassigned work items f) Issues
preventing progress? Call-in:
Toll-free dial-in: 1-877-421-0003 Toll dial-in: 1-770-615-1374
<For IBMers> Tie-line dial-in:
421-0003 Participant passcode:
667201 Thanks
Per Kroll
STSM, Manager Methods: RUP /
RMC
Project Lead: Eclipse Process Framework
Rational Software, IBM
Corp
408-342-3815
"Brian Lyons"
<blyons@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
06/13/2006 02:37 PM
|
Please respond
to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
|
To
| "Eclipse Process Framework Project
Developers List" <epf-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [epf-dev] Conference Call for
OpenUP/Basic package owners tomorrow |
|
hiho, Sorry for the last-minute notice. I would like to have a
conference call at 8am pacific time tomorrow (6/14/2006) for the OpenUP/Basic
package owners to touch base as a status update on open items to be done as part
of our 1.0 release. This is not meant to be a problem-solving call or anything.
It will just be a chance for each package owner to note how many process
elements were done in the last week, how many are left to be done overall, how
many are expected to be done in the next week, plus identify any
problems. The idea is to have the call tomorrow, then on Tuesday the
20th next week (to align well with the European Face to Face
meeting), then get in the habit of having them on each Wednesday until release
1.0. If a package-owner can’t make it onto the call, he should get the
“how many elements left to do” data sent out to epf-dev before the meeting so we
have a complete view across the OpenUP/Basic content. There has been some
verbal discussion of this amongst various key parties but based on the late
notice, we’ll consider this a dry run just to get the ball rolling. It is
certainly understandable if someone doesn’t make it on this first call.
For the
sake of transparency anyone can call in to observe, but it is expected that just
the committers responsible for the packages will participate. Though this
first call might be a bit sloppy, we are hoping to get these down to no more
than 30 minutes of status. The resulting data will be sent out to the
epf-dev list after the meeting.
Per Kroll is going to send out a subsequent message
with the conference call number. He might also have a tweak to what data I
have suggested be relayed in the call.
------------- b_______________________________________________
epf-dev mailing
list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
Attachment:
APG_ProcessComponentCompleteness_Guideline_v1_0.doc
Description: MS-Word document
