(→MeeGo SDK Documentation Team) |
m (→Ways of working) |
||
| Line 13: | Line 13: | ||
== Ways of working == | == Ways of working == | ||
| + | |||
=== Backlog === | === Backlog === | ||
| - | Currently, content planning is carried out in wiki.meego.com // | + | Currently, content planning is carried out in wiki.meego.com: [http://wiki.meego.com/Application_developer_site/Draft_content| Information structure]. Note that the plan is subject to change. |
| + | |||
| + | For MeeGo 1.2 release, documentation team will move to using Bugzilla/Featurezilla in tracking release content. | ||
Release content was initially divided into content areas, each with an owner. Content area owners are responsible for planning the content needs of their area. | Release content was initially divided into content areas, each with an owner. Content area owners are responsible for planning the content needs of their area. | ||
| Line 27: | Line 30: | ||
//More information about testing and review process to be added, later.// | //More information about testing and review process to be added, later.// | ||
| - | |||
== MeeGo 1.1 SDK documentation release == | == MeeGo 1.1 SDK documentation release == | ||
Contents |
MeeGo documentation team is a subteam of the MeeGo SDK team. The MeeGo SDK Documentation Team is responsible of providing documentation about developing for MeeGo platform.
Currently, content planning is carried out in wiki.meego.com: Information structure. Note that the plan is subject to change.
For MeeGo 1.2 release, documentation team will move to using Bugzilla/Featurezilla in tracking release content.
Release content was initially divided into content areas, each with an owner. Content area owners are responsible for planning the content needs of their area.
A buffer of two weeks before a release must be reserved for:
//More information about testing and review process to be added, later.//
This section will later include a backlog for following the MeeGo 1.1 documentation requirements and status.
Release planning is ongoing. Content areas and their owners are listed below: