RE: [epf-dev] IMPORTANT - OpenUP/Basic: due work and planned work

[Ricardo Balduino <balduino@xxxxxxxxxx>]

Chris, please see my comments below.

Ricardo Balduino
Senior Software Engineer

IBM | RUP Team | EPF Committer
Phone: 1 (408) 863-5019 (TL: 560-5019)

www.ibm.com
www.eclipse.org/epf

"Chris Armstrong" <chris.armstrong@xxxxxxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx

06/11/2006 09:46 PM

Please respond to
chris.armstrong@xxxxxxxxxxxxxxxxx; Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>

To	"'Eclipse Process Framework Project Developers List'" <epf-dev@xxxxxxxxxxx>
cc
Subject	RE: [epf-dev] IMPORTANT - OpenUP/Basic: due work and planned work

> Ricardo, since I haven't been versed in the where
and whyfores of CVS, here
> are some things that should be added to the list of OpenUP process
elements,
> as it relates to Project Management...
>  
> Checklist: Iteration Plan          
      
> Checklist: Project Plan          
      
> Concept: Phase (in base_concepts)
> Concept: Risk
> Example: Project Plan
> Example: Iteration Plan
> Example: Work Items List
> Guideline: Project Plan
> 
> In that spreadsheet, I might suggest putting templates inline with
each
> discipline instead of a separate section (#7)...

Chris, while you are not versed in CVS details, just send me a new version
of the spreadsheet and I update CVS for you. Could you please send me a
new version with the items above?


> I've just finished putting all the PM-related
bugs (and some extras -- looks
> like I added about 65 or so new items) in Bugzilla and it would be
nice if
> one could specify the discipline/domain as a part of the component
(instead
> of all items going into the "content" bucket). Like others,
I'm using a
> prefix (such as "PM") in the summary...

Interesting point, but I think components in Bugzilla are defined at a
higher level, like projects and sub-projects. Under content we could potentially
have OpenUP, Agile/XP, etc. as sub-components. Only the Eclipse web master
can create components, we should check with them.
As for now, its' a good idea to put the discipline
name as prefix of the bug description. It makes it easier to read and identify
related bugs.


>Also, I struggled with how to set bug attributes
like priority and severity,
>so I just took a stab at it... If you have any suggestions, let me
know...

Thanks for doing the initial classification of bugs
priority and severity. I can revisit the bugs you entered and follow the
same convention as found in: http://www.eclipse.org/epf/process/change_request_faq.php


>Thanks, Chris ~:|

________________________________

From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On
Behalf Of Ricardo Balduino
Sent: Monday, June 05, 2006 2:42 PM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] IMPORTANT - OpenUP/Basic: due work and planned work
Importance: High



Dear committers, 

We have important actions to take for OpenUP/Basic, please run the report
at
the bottom of this email, so you can have the data at hand: 

- M2: There is still one open issue related to M2 - we need closure on
this
asap. 
- M3: There are 5 issues. 
        - 2 are resolved, waiting to be closed 
        - 1 is assigned, should be resolved 
        - 2 are new, not even assigned to anyone 
- M4: From the 45 issues planned for M4, 31 haven't been assigned to anyone.

        - Package owners, if you have added entries,
please revisit them to
assign to interested contributors. In case you haven't added entries for
your package, please do so (yes, this number will be increased). 
        - Community, all contribution is welcome :-)

As you can see, we have a good volume of entries in Bugzilla that need
action (some due for M2 and M3, but most are planned for M4). Taking this
action early in M4 will help us to address the objectives for this
milestone. 

I'm also attaching 4 spreadsheets created by Chris Sibbald (thanks Chris)
that list all elements in need of content to be written. It is certainly
useful information for package owners to check completeness of their
packages. 

Link to the report: 

https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=priority&y_axis_field=
assigned_to&z_axis_field=target_milestone&query_format=report-table&short_de
sc_type=allwordssubstr&short_desc=&classification=Technology&product=EPF&com
ponent=Content&version=1.0&target_milestone=1.0+M2&target_milestone=1.0+M3&t
arget_milestone=1.0+M4&target_milestone=1.0+M5&long_desc_type=allwordssubstr
&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard
_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug
_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_
status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bu
gidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&form
at=table&action="">
mp;a!%20mp;type0-0-0=noop&value0-0-0= 

Please, don't hesitate to contact me (and this list) if you have any
question or comment. 
Thank you, 

Ricardo Balduino
Senior Software Engineer
IBM | RUP Team | EPF Committer

www.ibm.com
www.eclipse.org/epf 







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