2.x planning

Owned by Former user (Deleted)
Last updated: Sept 01, 2010 by Former user (Deleted)Version comment
1 min read

Draft

Sakai 2x Project Planning Goals
List of Planned 2.8.0 Changes

Location

Grand Mesa A, 2nd floor

Tentative Agenda

Morning (9 am - noon)

  1. Introduction with full group, then split into 2 and 3 tracks.
  2. 2.7 Post-Mortem and State of the Code (Alan)
  3. Cross-cutting concerns
    • Maintenance Team members, progress and proposals
    • Security issues (Noah)
    • Accessibility (Eli)
    • i18n ( ? )
  4. Release Management processes (Anthony)
    • Independent Releases
    • Continuous builds
    • ?
  5. Functional Areas
    • Gradebook services (in light of GB2, OnCourse gradebook front-end) - need shared ownership and maintenance
    • Planned development from tool teams
    • Assignments 2
    • OSP
  6. 2-3 Hybrid (Lance)

Afternoon (1 - 4 pm): a 2.8 plan

  1. List of priorities for 2.x, with estimates of resources needed and timelines
  2. Scoping a 2.8 from 2.x priorities
  3. Scoping a 2.9 from 2.x priorities
  4. Development required for this 2.8
  5. QA resources required for this 2.8
  6. Process changes that could deliver this 2.8
    • Calendar for this 2.8, with decision points

(this is what we will take to the community)