SDK/Toolchains

From MeeGo wiki

< SDK(Difference between revisions)

Latest revision as of 10:26, 1 February 2011

MeeGo Toolchain Team is responsible of toolchain for MeeGo Platform.

Meeting agendas, minutes, etc. can be found from SDK/Toolchains/Meetings

The following diagram figures out the process how the changes to the Toolchain components are done.

It contains a following roles:

MeeGo Community - self explaining role
Request Initiator - A stakeholder that wants to change version or add/remove of some component in the Toolchain.
MeeGo Toolchain WG - Toolchain working group in MeeGo
Partner - A stakeholder using the Toolchain

Most important deliverable is the Change Request (CR). It is filed by the Request Initiator and contains the following information:

Changed component
Version change
Business reason for the change
Use Case describing the change and what is achieved with the change
Test case(s) to validate the change. This should be a script that can be easily run and automated
Impact analysis where the change affects
Risks

The procedure step by step:

Request Initiator wants to change Toolchain and files the CR
Toolchain WG handles the CR, informs MeeGo community about the CR and pass the CR to the relevant Partners
Partner possibly handles it in their internal decision making body and checks at least the following:

* changed component is buildable
* executes performance tests
* checks that the packages can be built using the changed Toolchain

Report of the analysis is handled by the Partner and based on the results Partner gives verdict whether to approve or reject the CR.
Response is handled in the MeeGo Toolchain WG and the Request Initiator is informed. If the change has been approved the change is scheduled to be taken into use and the MeeGo community is informed about the upcoming change.
If the change has been rejected, the Request Initiator can escalate the change still (escalating path is TBD).

@@ Line 3: / Line 3: @@
 === Team ===
-* Jarmo Kant, Nokia (jarmo.kant@nokia.com), IRC: jake-k
+* Jarmo Kant, Nokia, IRC: jake-k
-* Austin Zhang, Intel (austin.zhang@intel.com), IRC: austin_zhang
+* Juha Kallioinen, Nokia, IRC: kaltsi
-* Al Nikolov, Nokia (al.nikolov@nokia.com)
+* Al Nikolov, Nokia
-* Alexander Kanevskiy, Nokia (alexander.kanevskiy@nokia.com)
+* Martti Lumme, Nokia, IRC: marlumme
-* Jan-Simon Möller, Linux Foundation (jsmoeller@linuxfoundation.org), IRC: dl9pf
+* Alexander Kanevskiy, Nokia
+* Leonid Moiseichuk, Nokia
+* Austin Zhang, Intel,IRC: austin_zhang
+* Jackie Wu, Intel
+* Jan-Simon Möller, Linux Foundation, IRC: dl9pf
+* Paavo Leinonen, Nokia
+=== Change Proposals ===
+* [[SDK/Toolchains/ToolchainChangeProposal]]
+=== Meetings ===
+Meeting agendas, minutes, etc. can be found from [[SDK/Toolchains/Meetings]]
-=== Things to do ===
-* Mode of operation (meetings, mailing lists, etc.)
-* Review of Toolchain Change Process
-* Team forming
-=== MeeGo toolchain Model ===
-MeeGo toolchain is based on the Baseline of Gnu-toolchain. Toolchain components of the MeeGo release is a snapshot of current toolchain version in the Baseline. The following figure shows the model in case of gcc compiler.
 === MeeGo Toolchain Change Process ===