Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Connection Info

  • Telephone (Sakai001): +1 812 856 7060  
  • Internet: 156.56.240.9
    • Conference Code: 348#
    • PIN: 72524#

Agenda

  1. 2.6.1 Release
    1. Testing update
    2. QA Servers
  2. 2.7.0
    1. Forums
    2. QA Servers
  3. New Filters
    1. filter review

Test Instances

Sakai 2.6.1 testing

New Jira Filters

How to use Jira confluence page 

Jira filter: fixed with no version issues

Release Proposal 2009

Google Spreadsheet of new features

New Feature Documentation

Attendees

Seth Theriault
Pete Peterson
Anthony Whyte
David Haines

David Horwitz

Michael Lockett

David Horwitz

Michael Lockett

Minutes

  • Update on 2.6.1 testing
  • Should we wait on release?
  • Jira filters from Anthony (http://confluence.sakaiproject.org/display/REL/Jira+filters+%282.6%29
  • Set a firm date for Sakai 2.6.1 release
  • Sakai 2.7
    • no firm release date or freeze date
    • no firm feature set yet; need a final list
    • Anthony put out Sakai-Trunk-QA branch (Seth's idea) this has the snapshot of the new Forums enhansements. This qa-trunk-branch will be refreshed often and at some point when the feature set for Sakai 2.7 is established we will create a formal Sakai-2.7.0-qa branch
    • This new trunk-qa branch will allow QA to test very early on the code for the upcoming release
  •  

Action Items - from 2009-09-17

  • Samigo blocker
  • Conversion scripts checked
  • K1 change review
  • Refresh QA branch
  • Additional servers running 2.6.x
  • Included issues for 2.5.6 and 2.6.1
  • Security issue review
  • Jira reviewers page
  • Filters page - community filters page

Action Items - 2009-09-24

  • email Sakai 2.6.1 update - Anthony
  • email to 2.6.1 branch managers - Anthony
  • email and calls to testers for 2.6.1 and trunk-qa
  • review the filter for 2.6.0-2.6.1 fixes and update as needed
  • the Release Meetings should include review of these filters (what is needed to test, what is ready to merge)
  • periodic email to the QA community on jira related issues
  • No labels