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 32 Next »

In Progress...

This page is under active development and is an exercise in trying to gather planning information that would be useful in creating roadmaps for the major/minor release scheme laid out in the Proposed Release Practice Guidelines, and as a result may be inaccurate in a number of areas. See Sakai 2.6 Roadmap for a view of similar information aligned with recent release practices.

Sakai Roadmap

  • A major release of Sakai would have a Feature Freeze two months before the code is frozen, branched from trunk, and a four to six month QA period begins.
  • A minor release of Sakai would have a Feature Freeze two weeks before the code is frozen, branched from trunk, and a one-month QA period begins.

Release Timeline

Dates below are only estimates; the further out, the less accurate. In particular because releases will dominantly be driven by features rather than dates.

First date is Feature Freeze, second date is Release Date.

Naming scheme is for illustrative purposes only. We need to find a good naming scheme still, but that shouldn't affect whether we decide to pursue the major/minor/maintenance release pattern.

  • 2.5 Major Release (October 2007/Febrary 2008)
    • 2.6 Minor Release (March 2008/April 2008)
    • 2.7 Minor Release (June 2008/July 2008)
  • 3.0 Major Release (September 2008/February 2009)
    • 2.9 Minor Release (October 2008/November 2008)
    • 2.10 Minor Release (December 2008/January 2009)
    • 3.1 Minor Release (March 2009/April 2009)
    • 3.2 Minor Release (June 2009/July 2009)
  • 4.0 Major Release (September 2009/February 2010)
    • 3.3 Minor Release (October 2009/November 2009)
    • 3.4 Minor Release (December 2009/January 2010)
    • ...

Feature Timeline

Estimated time at which a feature might be ready to be included in a release.

  • January 2008
    • Tools
      • WYSIWYG Widget (FCKeditor)
        • [Completed] FCKeditor upgrade to version 2.5.1, which brings in bug fixes and better Safari support.

      • Assignments2 (Indiana/Georgia Tech)
        • An initial iteration of new RSF-based "Assignments2"
        • Not intended as a replacement for existing Assignments tool, but similar to it.
  • February 2008
    • Tools
      • Mailtool
        • A new RSF-based version of the Mailtool (Georgia Tech, Carl Hall)
          • Available via Contrib?
      • SCORM Player (UC Davis, James Renfro; CRIM, Sacha Leprêtre)
        • A 2.5-compatible Contrib version for early adopters.
        • Supports SCORM 2004 3rd Edition.
  • March 2008
    • Cross-Project Activities
      • User Experience
        • Consistency of wording across tools (e.g., SAK-9410 - Getting issue details... STATUS : Add vs. New, SAK-9678 - Getting issue details... STATUS Remve vs. Delete)
    • Tools
      • Assignments2 (Indiana/Georgia Tech)
        • Second interation completed.
      • Checklist [Contrib] (University of Michigan, Dick Ellis)

        • An initial 1.0 release for use with Sakai.
  • August 2008
    • Tools
      • Assignments2 (Indiana/Georgia Tech)
        • Third iteration completed.
        • Expect this one to be ready for production; Indiana plans to only offer Assignments2 and not the original Assignments in their Fall 2008 semester.
        • Assignments and Assignments2 will not share the db schema; migration path is through site-to-site export/import.
        • User interface and overall workflow revamped, relative to Assignments.
        • Migration of grading functionality from Assignments2 into Gradebook, however, seamless workflow maintained by using Gradebook helpers in the context of Assignments2; may result in loosing some grading schemes that Assignments supported but Gradebook at this point does not.
      • Gradebook (Indiana/Georgia Tech)
        • Add helpers to support Assignment2's grading needs.
  • September/October 2008 (In time for next Major Release.)
    • Cross-Project Activities
      • Internationalization
        • Update translations (Beth Kirschner, Internationalization Working Group)
      • UX Improvement Project
        • Re-designed home page/landing page effort (Sakai Foundation, Fluid Project)
    • Tools
      • Assignments
        • Refactoring of db to improve performance; involves moving selected meta data from XML blob into table columns and supporting migration code. (UM)
      • Assignments2
        • A more complete version of "Assignments2" (Indiana/Georgia Tech)
      • Email Archive
        • Develop performance improvements for when there are a large number of messages in the archive. (Charles Severance)
      • Resources
        • Initial Fluid redesign of as-yet-undetermined components associated with Resources UX. (Fluid Project)
        • Resource Viewer/Content Viewer version for early adopters. (Joshua Ryan, Mike Osterman)
          • In Contrib?
          • Add helper based on entity broker to help in sequencing content for viewer. (Joshua Ryan)
      • Samigo
        • Allow editing a published assessment. (Stanford)
        • Add ability to release assessments to groups. (UCT)
      • User Membership (Currently Provisional)
        • Include the created and last modified date on the screen and in the CSV export. (UFP, Nuno Fernandes)
        • Filtering the searching and viewing of users to only those users with the same named usertype(s). (UFP, Nuno Fernandes)
      • WYSIWYG Widget (FCKeditor)
        • FCKeditor plug-in to allow users to embed entities. (Joshua Ryan)
    • Services
      • Component
        • Support for more flexible configuration of components, SAK-8315. (Berkeley, Ray Davis)
      • Content Hosting Service
        • JCR implementation, testing and migration. (Cambridge)
      • Portal
        • Develop an iFrame portlet that will completely replace the tool iFrame; this will eliminate one frame for web content tools. (University of Michigan, Charles Severance)
        • Add a new view which allows a tool to request that it be shown maximized and in a frame set rather than an iFrame; helpful for things like publisher content, SCORM players, etc. that already have left-hand buttons and in preventing double scroll-bars. (University of Michigan, Charles Severance)
    • Non-Release Related Work in this Time-Frame
      • When the 2.5 portal solidifies, create post-2.3 and post-2.4 branches to make its functionality available to those running Sakai 2.3 and 2.4. (University of Michigan, Charles Severance)
  • Early-2009
    • "Assignments2" delivered (Indiana/Georgia Tech)
      • Is it a replacement of Assignments? Is it a separate tool to be used in conjunction with Assignments? Is it an alternative, choose to use either Assignments or Assignments2?
  • Mid-2009
    • Gallery (Berkeley)

Future Work

These are features and functionality that folks are working on (or plan to start work on) for which they do not have a good estimate for completion at this time, but which is likely to be more than a year away.

  • Off-line Sakai (?)
    • Ability to work with a local copy of Sakai (i.e., on your laptop, disconnected from the network) and sync between the local copy and your Sakai installation.
  • OpenCast (Berkeley)
    • A podcast capture, post-processing, and distribution system that will integrate current technological advancements, such as Apple's Podcast Producer, with existing academic community source frameworks, such as Sakai.
  • Site Hierarchy (Oxford)
    • A service that allows sites to be arranged into a hierarchy (sites can exist at multiple nodes in a hierarchy or be their own single-point hierarchy) and manages the permissions on creation/updating the hierarchy.
    • A set of tools that allow you to manage a hierarchy of sites.
    • Development of a helper tool versions of SiteSetup (Site Info, Worksite Setup) and the site browser so that they can easily be embedded in a workflow.
    • A custom portal handler to support the /hierarchy namespace.

Possible Work

These are features and functionality that folks are interested in collaborating on, but which they have not yet committed to working on.

  • "Dashboard" views cutting across all sites; probably start with Assignments. (Georgia Tech)
  • Zimbra calendar integration with Schedule tool. (Georgia Tech)
  • Absorbing Mailtool into a new Email Archive tool (as a composition screen). (Georgia Tech)

Related Projects

Adopter Timelines

Adopter

Tentative Timeline

University of Cape Town

2.4 to 2.5 December 2007

Rutgers University

2.3 to 2.5 May 2008

Georgia Tech

2.4 to 2.5 May 2008

University of Michigan

2.4 to 2.5 August 2008

University of California, Davis

2.4 to 2.5 September 2008

Australian National University

2.4 to 2.5 mid- to late- 2008

  • No labels