EPF Content Call – April 09, 2008.

Participants:

Kim Werner
Bjorn Gustafsson
Jim Ruehlin
Margaret Hedstrom
Ricardo Balduino
David Hadley

Agenda

1. Method Authoring guidelines 
        - collect feedback from committers on the method authoring guidelines sent 2 weeks ago 
        - Q&A (Kelli Houston will join us) 
2. Release plan: 
        - Fine-tune the release plan we started last week 
        - Get commitment/ideas for current iteration from those who couldn't attend last call 
3. Next release number 
        - Report from folks who discussed this topic on Monday 
        - Discuss open issues they raised 

Discussion / actions (in red)

1. Method Authoring Guidelines

o	We didn’t discuss/collected feedback from committers on the Method Authoring guidelines – not all committers who received the guidelines were on the call.
o	Please, everyone review guidelines for discussion next week. We will invite Kelli to join.
o	Ricardo will send method authoring guidelines to Kim and Margaret.

2. Release Plan

o	Not all committers responsible for one or more practices were able to join the call today.
o	Evolutionary Design weekly calls have been scheduled and made available in Yahoo calendar.
o	Architecture weekly calls will start as well.
o	PM calls to start soon – Ricardo to synch up with Ana and Bjorn, and post a list of Bugzilla issues for PM practices.

o	Bruce mentioned that RMC Beta is coming in May, and will ship with the EPF Practice library
o	In EPF release plan, consider some freeze dates where stable content can be pulled out to be included in the beta tool.
o	Bruce will send info about freeze dates and Ricardo will post it.

o	EPF 1.5 (initial build) will be made available for test late in April
o	Build is now being tested by EPF developers
o	It should be safe to move to this build (requires library upgrade) – EPF Composer team is committed to address problems we find
o	We should post a pre-build to EPF committers to test soon

o	Regarding Bugzilla, should we create another component to capture Practice Library work? 
o	The decision was that we don’t need it, since it adds complexity
o	We will use the same Content component, but add acronyms to the bug description to make queries easier.
o	Jim will propose a list of acronyms for the practice library. 

3. Next Release Number

o	It has been proposed that all processes should have same version number
o	e.g. OpenUP 1.5 published out of Prac Library 1.5
o	from same Practice Library, one publishes e.g. Scrum 1.5 and OpenUP 1.5
o	pros: easy formula for maintenance
o	cons: version number bumped without any change to content
o	tool dependency: it means process has been published with EPFComposer 1.5
o	Other line of thinking: 
o	what matters is that each practice should reflect if there were major changes or not, and not necessarily tie to the tool version number
o	companies will ship different versions of the library with different versions of the tool
o	practice library needs a version number, but individual practices don’t
•	maintaining version number on plug-ins becomes difficult (number of plug-ins)
o	No agreement was reached – discussion proposed to be continued on a separate small group – Jim to lead