You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

1. Roadmap and Feature Planning

Based on OpenSUSE section 1.

Purpose

  • To create the initial time-line for the release: the roadmap.
  • To define/update the platform functional requirement.
  • To identify the main technical goals for the new release.

Entry Criteria

  • E1.1 Previous release version of the distribution was released.

Tasks

  • T1.1 Create the roadmap and platform functional requirement specification. 

A detailed description about the rules used to build the roadmap and platform functional requirement is in [xx]. These document need to be written in AGL confluence.

  • T1.2 Feature freeze calendar. 

Together with the roadmap calendar is the associated feature freeze calendar.  There are three stages of freezing: toolchain freeze after M3, base system freeze after M4 and full feature freeze after B1.  After that the quality assurance process starts.

  • T1.3 Determine the new features.

On the AGL Instrument Cluster Expert Group the new features expected for this release are discussed and defined. As a result new version of the platform functional requirement specification will be released.  This spec must be created before architecture development phase.

Verification

  • V1.1 Review the platform functional requirement

The platform functional requirement needs to be approved by at least half of the SAT (System Architecture Team) core members and at least half of the SC (Steering comity) members.

  • V1.2 Review the roadmap.

The roadmap needs to be approved by the Product Manager(Walt?) and the Instrument Cluster Expert Group Leader(Haraki-san?).

  • V1.3 Platform functional requirement and roadmap maintenance.

Small changes in the roadmap are not communicated, just executed.  But if a delay threatens the release day, an announcement is expected, and if the delay is serious we need to communicate it widely.
When the platform function is dropped from initial platform functional requirement, it must be approved by at least half of the SAT (System Architecture Team) core members.  After that platform functional requirement specification must be update.

Exit Criteria

  • X1.1  The platform functional requirement specification and the roadmap calendar are fixed and freezed.

Deliverables

  • D1.1  The platform functional requirement specification is published in AGL confluence.
  • D1.2  The roadmap calendar is published in AGL confluence.


2. 




  • No labels