m |
m |
||
| Line 19: | Line 19: | ||
== Status summaries == | == Status summaries == | ||
| + | |||
| + | * [SDK/Meetings#Weekly_meetings| Status reports from documentation weekly meetings] | ||
| + | * Status of individual pages is available in [[Documentation_Backlog_for_MeeGo_1.2 | Documentation_Backlog_for_MeeGo_1.2]] | ||
| + | |||
== Milestones and schedules == | == Milestones and schedules == | ||
| + | The documentation work is planned, carried out, and finalized in sync with MeeGo SDK releases. | ||
| + | //add link to SDK schedules// | ||
| + | |||
== Risks == | == Risks == | ||
| + | |||
== Quality plan == | == Quality plan == | ||
| Line 33: | Line 41: | ||
== Maintenance plan == | == Maintenance plan == | ||
| + | |||
| + | //add information about Bugzilla and how documentation bugs are handled and prioritized.// | ||
== Ways of working - instructions for documentation team members == | == Ways of working - instructions for documentation team members == | ||
| Line 46: | Line 56: | ||
== Information about earlier releases == | == Information about earlier releases == | ||
| + | |||
=== Requirements for MeeGo 1.1 SDK documentation release=== | === Requirements for MeeGo 1.1 SDK documentation release=== | ||
Contents
|
MeeGo documentation team is a subteam of the MeeGo SDK team that is responsible of providing documentation about developing for MeeGo platform. The documentation work is planned, carried out, and finalized in sync with MeeGo SDK releases.
The documentation work is planned, carried out, and finalized in sync with MeeGo SDK releases. //add link to SDK schedules//
A buffer of two weeks before a release must be reserved for:
//More information about testing and review process to be added, later.//
//add information about Bugzilla and how documentation bugs are handled and prioritized.//
To allow archiving content for previous releases as well as finding any new content conveniently, we plan to organize the pages as follows:
For MeeGo 1.1 release: