Skip to end of metadata
Go to start of metadata


Rice Release 1.1

Key Themes for Release 1.1: Version Compatibility, Modularity, Ease of Implementation, Kuali Application Business Drivers, Industry Standards, Usability.

Assumptions:

  • September 2010 Release Date
  • 850 developer hours per month capacity
  • 50% of capacity, 3825 developer hours, available for roadmap work (5% reserved for work on 1.0.x, 20% reserved for bug fixes in prior releases, 25% reserved for QA work on 1.1)
    type key summary fixVersions customfield_10917

    Unable to locate JIRA server for this macro. It may be due to Application Link configuration.

Rice Release 1.2

Key Themes for Release 1.2: Modularity, Development Ease of Use, Usability, Kuali Application Business Drivers, Ease of Implementation, Service Orientation, Version Compatibility.

Assumptions:

  • April 2011 Release Date
  • 850 developer hours per month capacity
  • 50% of capacity, 3000 developer hours, available for roadmap work (5% reserved for work on 1.1.x, 20% reserved for bug fixes in prior releases, 25% reserved for QA work on 1.2)
    type key summary fixVersions customfield_10917

    The URL filter is not available to you, perhaps it has been deleted or had its permissions changed

Rice Release 2.0

Key Themes for Release 2.0: Development Ease of Use, Platform Support, Kuali Application Business Drivers, Service Orientation, Ease of Implementation, Modularity, Internationalization, Industry Standards, Usability, Project Standardization, Adopting Existing Code.

Assumptions:

  • April 2012 Release Date
  • 850 developer hours per month capacity
  • 50% of capacity, 5100 developer hours, available for roadmap work (5% reserved for work on 1.2.x, 20% reserved for bug fixes in prior releases, 25% reserved for QA work on 2.0)
    type key summary fixVersions customfield_10917

    Unable to locate JIRA server for this macro. It may be due to Application Link configuration.

All Unplanned Future Enhancements and Research

type key summary fixVersions customfield_10917

Unable to locate JIRA server for this macro. It may be due to Application Link configuration.

1 Comment

  1. A thought on this... I really like the use of JIRA.

    It would be great if we could leverage the "Vote" feature of JIRA to gauge community interest on particular enhancements.

    Or maybe create buckets where one is top priority items for the foundation and its projects (i.e. no JIRA voting), and another bucket of enhancements for the community to vote on.