m (→MeeGo 1.1 SDK documentation release) |
m |
||
| Line 24: | Line 24: | ||
=== Backlog === | === Backlog === | ||
| - | |||
For MeeGo 1.2 release, documentation team will move to using Bugzilla/Featurezilla in tracking release content. | 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. | + | For MeeGo 1.1 release: |
| + | * 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. | ||
| + | * [[Developer_Guide_for_MeeGo_1.1]] functions as a backlog for following the MeeGo 1.1 documentation requirements, responsibilities, and status of individual pages. | ||
| + | |||
=== Reviews and content verification=== | === Reviews and content verification=== | ||
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.
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.2 release, documentation team will move to using Bugzilla/Featurezilla in tracking release content.
For MeeGo 1.1 release:
A buffer of two weeks before a release must be reserved for:
//More information about testing and review process to be added, later.//
Developer_Guide_for_MeeGo_1.1 functions as a backlog for following the MeeGo 1.1 documentation requirements, responsibilities, and status of individual pages.