[[BackLinksMenu]]

[[TicketQuery(summary= UNPLANNED_FEATURE_SCHEDULE_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]



= Analysis =

== Overview ==
Provide a schedule of releases that acts as an overview for the project to ensure the project is on track.

== Task requirements ==
The release schedule document needs to give an overview of each release, including:

* What can be expected to be functioning in each release
  * This does not need to be overly detailed, as it is very hard to guess every feature that will be completed due to unforeseen issues
  * We want this to be a guideline that others can use to ensure the health of the project
* When each release will be made available

== Task result ==
Document approved by the team and Nick giving an overview of the schedule and what can be expected in each release.

== Implementation idea ==
The schedule data will be collected from the task index, the resources spreadsheet and from Milo.

== Related ==
[wiki:UNPLANNED_FEATURE_SCHEDULE_REVIEW_R0]

[wiki:UNPLANNED_FEATURE_SCHEDULE_DELIVERY_R0]

== How to demo ==
Provide a link to the document, and email the link to the team for [wiki:UNPLANNED_FEATURE_SCHEDULE_REVIEW_R0].

The schedule can be found here: [wiki:ReleaseSchedule]

= Design =

= Implementation =
^(Implementation results should be described and linked here (from the wiki or the repository))^

= Testing =

N/A

= Comments =
^(Write comments for this or later revisions here.)