SDK/Toolchains

Revision as of 11:22, 19 November 2010 (view source) Kant (Talk | contribs) ← Older edit		Revision as of 11:24, 19 November 2010 (view source) Kant (Talk | contribs) Newer edit →
Line 18:		Line 18:
	=== Meetings ===		=== Meetings ===
-	Regular project meeting every second Friday @08.00 - 09.00 UTC. Next meeting is 2010-12-03.	+	Meeting agendas, minutes, etc. can be found from [[SDK/Toolchain/Meetings]]
-		+
-	Working environment at Piratepad http://piratepad.net/I4eNvGQxWR	+
-		+
-	Friday, 2010-11-19 @8.00 - 9.00 UTC: [[SDK/Toolchains/Meetings/Notes20101119]]	+
-	Monday, 2010-11-08 @9.30 - 10.30 UTC: [[SDK/Toolchains/Meetings/Notes20101108]]	+
-	Friday, 2010-10-22 @9.30 - 10.30 UTC: [[SDK/Toolchains/Meetings/Notes20101022]]	+
-		+
-	Agenda:	+
-		+
-	0) Pointers to Mails / Discussion	+
-		+
-	1) How to ensure optimized toolchain for x86 and ARM	+
-	* Patchsets (also Linaro usage)	+
-	* Update Roadmap	+
-	* CFlags, softfloat, hardfloat	+
-		+
-	2) Toolchain in SDK and OBS	+
-	* Responsibilities (OBS + SDK)	+
-		+
-	3) Toolchain releasing	+
-	* Update rules	+
-		+
-	4) Open issues	+
-		+
-	5) AOB	+
-		+
-	=== 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 mainstream of GNU-toolchain. The same Toolchain is used for x86 and ARM architectures. Nokia is responsible for ARM patches and Intel for x86 patches.	+
-		+
-	Before the Toolchain can be accepted to MeeGo Release, the MeeGo related patches (from x86 and ARM) must be accepted into upstream.	+
-		+
-		+
-		+
-		+

---

Revision as of 11:24, 19 November 2010

Contents 1 MeeGo Toolchain 1.1 Team 1.2 Change Proposals 1.3 Meetings 1.4 MeeGo Toolchain Change Process

MeeGo Toolchain

MeeGo Toolchain Team is responsible of toolchain for MeeGo Platform.

Team

• Jarmo Kant, Nokia (jarmo.kant@nokia.com), IRC: jake-k
• Juha Kallioinen, Nokia (juha.kallioinen@nokia.com)
• Al Nikolov, Nokia (al.nikolov@nokia.com)
• Martti Lumme, Nokia (martti.lumme@nokia.com), IRC: marlumme
• Alexander Kanevskiy, Nokia (alexander.kanevskiy@nokia.com)
• Leonid Moiseichuk, Nokia (leonid.moiseichuk@nokia.com)
• Austin Zhang, Intel (austin.zhang@intel.com), IRC: austin_zhang
• Jackie Wu, Intel (jackie.wu@intel.com)
• Jan-Simon Möller, Linux Foundation (jsmoeller@linuxfoundation.org), IRC: dl9pf

Change Proposals

• SDK/Toolchains/ToolchainChangeProposal

Meetings

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

MeeGo Toolchain Change Process

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

Change request template: File:Toolchain cr template.txt

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).