Reference:What are the Release Notes Documents?: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
innovaphone publishes the then-current [[Support:DVL-Roadmap|development roadmap]] on a daily basis in this wiki.
innovaphone publishes the then-current [http://wiki.innovaphone.com/index.php?search=roadmap roadmaps] on a daily basis in this wiki.


This document reflects the current status of development and planning.  It thus may change without notice (except that any changes will be published in an update of this roadmap).  All entries reflect current thinking.  '''In no way are they intended as a commitment, neither with respect to planned functionality, nor to delivery dates'''.
These documents reflect the current status of development and planning.  It thus may change without notice (except that any changes will be published in an update of this roadmap).  All entries reflect current thinking.  '''In no way are they intended as a commitment, neither with respect to planned functionality, nor to delivery dates'''.


Then again, the roadmap contains most valuable information to our partners.  It shows what our current thinking is, which feature requests did make it into the roadmap and what priority is assigned to it.  Also, it will indicate if or if not an item is being worked on, or has been completed even.
Then again, the roadmaps contain most valuable information to our partners.  It shows what our current thinking is and which feature requests did make it into the roadmap.  Also, it will indicate if or if not an item is being worked on, or has been completed even.


If you need to know what is going on with innovaphone's product development, this is the right source.  If you need to give commitment to your customers, it is not.
If you need to know what is going on with innovaphone's product development, this is the right source.  If you need to give commitment to your customers, it is not.


== Format and Structure ==  
== Format and Structure ==  
The roadmap is structured in chapters, each describing a forthcoming major milestone.  This is usually
There is one roadmap article per project (e.g. a specific firmware major release version).
* the hotfixes for the current (service) release (for a more complete definition of these terms, see the [[Howto:How the build number scheme works|description of the build numbering scheme]])
The roadmap is structured in chapters, each describing a forthcoming major milestone.   
* the upcoming service release and releases
* planned hardware releases


For each item, there may be a deadline, indicated in the chapters headline (such as ''07/44'' (year/week) in [[Support:DVL-Roadmap#07/44_SR2:_Diagnostics|07/44 SR2: Diagnostics]]).  This is our best estimate as of now, again it is not intended as a delivery date commitment.  
For each item, there may be a deadline, indicated in the chapters headline (such as ''07/44'' (year/week)).  This is our best estimate as of now, again it is not intended as a delivery date commitment.  


Each chapter has a number of subchapters describing items that we think are of major interest to everyone.  However, there will allways be a number of issues that are not of general interest, but may be nonetheless of utmost importance to some of our partners.  Those items are summarized briefly under the [[Support:DVL-Roadmap#Other Items for 07/44 SR2: Diagnostics|Other Items for ''xxx'']] heading.
Each chapter has a number of subchapters describing items that we think are of major interest to everyone.  However, there will allways be a number of issues that are not of general interest, but may be nonetheless of utmost importance to some of our partners.  Those items are summarized briefly under the ''Other ...'' heading.


Each issue shows the following properties:
Each issue shows the following properties:


{|
{|
| Assigned  || user
|-
| Status  || <nowiki>{ Assigned | Feedback | Resolved | Closed }</nowiki>
| Status  || <nowiki>{ Assigned | Feedback | Resolved | Closed }</nowiki>
|-
| Priority  || <nowiki> { low | </nowiki>''none'' <nowiki>| normal  | high | urgent | immediate }</nowiki>
|-
|-
| Id || ''number''
| Id || ''number''
Line 37: Line 31:


== Related Articles ==
== Related Articles ==
[[Support:DVL-Roadmap]]
[http://wiki.innovaphone.com/index.php?search=roadmap Roadmap Articles]

Revision as of 19:16, 1 June 2010

innovaphone publishes the then-current roadmaps on a daily basis in this wiki.

These documents reflect the current status of development and planning. It thus may change without notice (except that any changes will be published in an update of this roadmap). All entries reflect current thinking. In no way are they intended as a commitment, neither with respect to planned functionality, nor to delivery dates.

Then again, the roadmaps contain most valuable information to our partners. It shows what our current thinking is and which feature requests did make it into the roadmap. Also, it will indicate if or if not an item is being worked on, or has been completed even.

If you need to know what is going on with innovaphone's product development, this is the right source. If you need to give commitment to your customers, it is not.

Format and Structure

There is one roadmap article per project (e.g. a specific firmware major release version). The roadmap is structured in chapters, each describing a forthcoming major milestone.

For each item, there may be a deadline, indicated in the chapters headline (such as 07/44 (year/week)). This is our best estimate as of now, again it is not intended as a delivery date commitment.

Each chapter has a number of subchapters describing items that we think are of major interest to everyone. However, there will allways be a number of issues that are not of general interest, but may be nonetheless of utmost importance to some of our partners. Those items are summarized briefly under the Other ... heading.

Each issue shows the following properties:

Status { Assigned | Feedback | Resolved | Closed }
Id number
description

A Feedback status indicates some clarification that is still required. Resolved and Closed indicate that the issue has been completed.

An immediate priority indicates an item that is currently being worked on (unless it is Resolved or Closed).


Related Articles

Roadmap Articles