Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Aperi Development Status Meeting 10/01/07"

 
Line 2: Line 2:
 
[http://wiki.eclipse.org/index.php/Aperi/meetings Aperi Meetings]
 
[http://wiki.eclipse.org/index.php/Aperi/meetings Aperi Meetings]
 
[http://wiki.eclipse.org/index.php/Aperi_Development_Meetings Aperi Development Meetings]
 
[http://wiki.eclipse.org/index.php/Aperi_Development_Meetings Aperi Development Meetings]
== Dial in numbers: ==
 
<big>
 
Toll Free: <FONT COLOR="red">'''877-421-0029'''</FONT>   
 
asInternational: <FONT COLOR="red">'''770-615-1246'''</FONT>
 
Passcode: <FONT COLOR="red"> '''800415''' </FONT>
 
</big>
 
<!-- COMMENT
 
 
== Attendees: ==
 
== Attendees: ==
 
+
'''Brocade''' John Crandall , '''IBM''' (Brenda Haynes, Dave Wolfe, Greg McBride, Tom Guinane, Hans Lin, Todd Singleton) , '''LSI''' (Jenny Monessen)   
'''IBM''' (Brenda Haynes, Dave Wolfe, Greg McBride, Ramani Routray, Tom Guinane) , '''LSI''' (Jenny Monessen)   
+
 
+
 
== Minutes: ==
 
== Minutes: ==
COMMENT -->
 
 
== Agenda: ==
 
 
 
* Project Leader Notes:  
 
* Project Leader Notes:  
** SAN Simulator contribution:  tasks to availability:  
+
** SAN Simulator contribution:   
*** Massaging the scripts and getting the build to work in the Aperi environment.
+
*** Tom and Todd worked up a list of tasks to make the download available:  
*** Tweaking the install procedure
+
**** Massage the scripts and get the build to work in the Aperi environment.
*** Testing the install
+
**** Tweak the install procedure
*** Testing the SAN Simulator
+
**** Test the install
*** Reviewing the Install documentation and making updates
+
**** Test the SAN Simulator
*** Reviewing the User Guide and making updates
+
**** Review the Install documentation and make updates
*** Updating the download web page to reorganize and add the SAN Simulator
+
**** Review the User Guide and make updates
*** Test download, install, and tool from user perspective
+
**** Update the download web page to reorganize and add the SAN Simulator
*** Announce availability of the SAN Simulator
+
**** Test download, install, and tool from user perspective
 +
**** Announce availability of the SAN Simulator
 +
*** Todd to provide timeframes for these and Tom will add to the schedule
 +
*** After discussion, it was decided that the SAN Simulator will have its own release numbering, independent of the SRM framework code.  It will start with release 0.1
 
** Third Party Contribution Questionnaires
 
** Third Party Contribution Questionnaires
 +
*** No new updates
 
** Aperi Open Defects - [https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=bug_severity&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Aperi&short_desc=&short_desc_type=allwordssubstr&type0-0-0=notequals&value0-0-0=&votes=&= by priority ]
 
** Aperi Open Defects - [https://bugs.eclipse.org/bugs/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=bug_severity&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Aperi&short_desc=&short_desc_type=allwordssubstr&type0-0-0=notequals&value0-0-0=&votes=&= by priority ]
 +
*** 199148 – Dave will look at, but currently there is a work around
 +
*** Dave set up a prioritization scheme.  Please see his append on the wiki.
 +
*** Dave asked that we redo the query to sort by priority first then by severity.
 
** Road map planning
 
** Road map planning
 
*** [http://wiki.eclipse.org/Release_Planning requirements list]  
 
*** [http://wiki.eclipse.org/Release_Planning requirements list]  
 
*** [http://wiki.eclipse.org/Road_map_update_timeline timeline]
 
*** [http://wiki.eclipse.org/Road_map_update_timeline timeline]
 
*** [http://wiki.eclipse.org/images/a/af/Aperi_Roadmap_DRAFT_092707.pdf Road map DRAFT]
 
*** [http://wiki.eclipse.org/images/a/af/Aperi_Roadmap_DRAFT_092707.pdf Road map DRAFT]
 +
**** A draft Aperi roadmap update is available on the wiki (http://wiki.eclipse.org/images/a/af/Aperi_Roadmap_DRAFT_092707.pdf).  This first cut takes into account all the feedback from those who have responded with discussions on aperi-dev and those that have responded with prioritized requirements as well as the discussion at our weekly development team and bi-weekly community meetings.  It also folds in the survey feedback, http://dev.eclipse.org/mhonarc/lists/aperi-survey/maillist.html , as well. 
 +
**** The draft roadmap has a number of open questions.  We reviewed the roadmap and discussed options for approval.  Some members would like a few more days to review.  Tom will post the options on aperi-dev prior to a vote this week.  We are still targeting to have this completed by 10/12. 
 
*** Road map vote  
 
*** Road map vote  
** R0.4 content closure
+
**** As part of our processed we vote on roadmap changes.  As we are not ready to close on a completely booked roadmap, we discussed taking a vote on different levels of completion for each release:
 +
****# For 4Q07, a yes vote means this will be booked
 +
****# For 2Q08, a yes vote means we will gain agreement on the content for this timeframe by the end of October. 
 +
****# For follow on activities, we will gain agreement on the priority line items by the end of October.
 +
**** The team agreed to pursue the above voting scenario.
 +
** R0.4 content closure will take place as part of the voting process above.
  
 
* Release Engineer Notes (Todd):   
 
* Release Engineer Notes (Todd):   
 
** Build status
 
** Build status
 +
*** No additional builds last week.
  
 
* Aperi Downloads:
 
* Aperi Downloads:
Line 46: Line 48:
  
 
* Development items/issues:
 
* Development items/issues:
 +
** Noting this week.
  
 
* IDVT:  
 
* IDVT:  
 
** [http://wiki.eclipse.org/index.php/Aperi/Test/Status Test Status
 
** [http://wiki.eclipse.org/index.php/Aperi/Test/Status Test Status
 +
** Hans to reevaluate the test plan based on the revised content for R0.4.
  
 
* ID:
 
* ID:
 
** Online help issue: Eclipse based or Java help based?
 
** Online help issue: Eclipse based or Java help based?
 
** ID plan for R4
 
** ID plan for R4
 +
*** Chris to reevaluate the ID plan based on the revised content for R0.4.
  
 
* Project Schedule:
 
* Project Schedule:
 
** Latest [http://wiki.eclipse.org/index.php/Aperi_Project_Schedule Schedule].  Items updated in the schedule
 
** Latest [http://wiki.eclipse.org/index.php/Aperi_Project_Schedule Schedule].  Items updated in the schedule
** Follow-on [http://wiki.eclipse.org/index.php/Release_Planning release planning]
 
  
 
* Action Items:
 
* Action Items:
Line 90: Line 94:
 
* Open Forum:
 
* Open Forum:
 
* Other:
 
* Other:
** Next Meeting - 10/8/07 ***
+
** Next Meeting - 10/8/07  
 +
*** Tom will be out 10/5 and will return 10/11.  Looking for someone to run the call next week.

Latest revision as of 17:41, 1 October 2007

Aperi Wiki Home Aperi Meetings Aperi Development Meetings

Attendees:

Brocade John Crandall , IBM (Brenda Haynes, Dave Wolfe, Greg McBride, Tom Guinane, Hans Lin, Todd Singleton) , LSI (Jenny Monessen)

Minutes:

  • Project Leader Notes:
    • SAN Simulator contribution:
      • Tom and Todd worked up a list of tasks to make the download available:
        • Massage the scripts and get the build to work in the Aperi environment.
        • Tweak the install procedure
        • Test the install
        • Test the SAN Simulator
        • Review the Install documentation and make updates
        • Review the User Guide and make updates
        • Update the download web page to reorganize and add the SAN Simulator
        • Test download, install, and tool from user perspective
        • Announce availability of the SAN Simulator
      • Todd to provide timeframes for these and Tom will add to the schedule
      • After discussion, it was decided that the SAN Simulator will have its own release numbering, independent of the SRM framework code. It will start with release 0.1
    • Third Party Contribution Questionnaires
      • No new updates
    • Aperi Open Defects - by priority
      • 199148 – Dave will look at, but currently there is a work around
      • Dave set up a prioritization scheme. Please see his append on the wiki.
      • Dave asked that we redo the query to sort by priority first then by severity.
    • Road map planning
      • requirements list
      • timeline
      • Road map DRAFT
        • A draft Aperi roadmap update is available on the wiki (http://wiki.eclipse.org/images/a/af/Aperi_Roadmap_DRAFT_092707.pdf). This first cut takes into account all the feedback from those who have responded with discussions on aperi-dev and those that have responded with prioritized requirements as well as the discussion at our weekly development team and bi-weekly community meetings. It also folds in the survey feedback, http://dev.eclipse.org/mhonarc/lists/aperi-survey/maillist.html , as well.
        • The draft roadmap has a number of open questions. We reviewed the roadmap and discussed options for approval. Some members would like a few more days to review. Tom will post the options on aperi-dev prior to a vote this week. We are still targeting to have this completed by 10/12.
      • Road map vote
        • As part of our processed we vote on roadmap changes. As we are not ready to close on a completely booked roadmap, we discussed taking a vote on different levels of completion for each release:
          1. For 4Q07, a yes vote means this will be booked
          2. For 2Q08, a yes vote means we will gain agreement on the content for this timeframe by the end of October.
          3. For follow on activities, we will gain agreement on the priority line items by the end of October.
        • The team agreed to pursue the above voting scenario.
    • R0.4 content closure will take place as part of the voting process above.
  • Release Engineer Notes (Todd):
    • Build status
      • No additional builds last week.
  • Development items/issues:
    • Noting this week.
  • ID:
    • Online help issue: Eclipse based or Java help based?
    • ID plan for R4
      • Chris to reevaluate the ID plan based on the revised content for R0.4.
  • Project Schedule:
    • Latest Schedule. Items updated in the schedule
  • Action Items:
]-
Item Owner Target Status
Obtain two mentors Tom 10/31/07 Per new development process rules, we need to obtain two project mentors. Harm Sluiman is one. Tom is searching for additional candidate.
Aperi Forum Tom 10/25/07 Suggested by Javier. Investigate setting up forums for Aperi communication. Looked into freepowerboards.com Friendly, easy to use, familiar to more forum users. Also includes a chat tool. Set up a sample forum http://www.freepowerboards.com/dhiwa/ Take a look and provide feedback. Checking out Eclipse IRC again
Document Control Tom 11/6/07 Write up text for Aperi document control.
Lessons Learned Follow-up Tom 11/9/07 Put results of Lessons Learned meeting for R0.3 into a table on the wiki with corresponding action items
cvs download statistics Tom 10/3/07 Investigate if we can get any numbers for our source code downloads.
  • Open Forum:
  • Other:
    • Next Meeting - 10/8/07
      • Tom will be out 10/5 and will return 10/11. Looking for someone to run the call next week.

Back to the top