MeeGo wiki - User contributions [en]

Release Engineering/Plans/1.2

2011-07-28T20:23:39Z

Uhofemeier:

== MeeGo 1.2 Release Plan (1.2.0, 1.2.1) ==

[[File:MeeGoReleaseTimeline1.2.x.jpg]]

=== Detailed summary ===

1.2.0 will be branched on May-01-2011 and released on May-19-2011.

1.2 will keep moving forward towards the 1.2.1 release.

1.2.0-Updates will be cherry-picked by the Meego Update team from the 1.2 Branch into 1.2.0.Updates.

1.2.1 will be branched around Aug-10-2011 and released around Sep-01-2011. The release will include the MeeGo Repos and Tablet 1.2.1 images.

1.2.1-Updates will then be cherry-picked by the Meego Update team from the 1.3 Branch into 1.2.1.Updates. At this point, 1.2.0.Updates will also be cherry-picked by the Meego update team.

1.2.1 will be the end of the 1.2-based releases.

=== FAQ ===

''Note: for all responses below, any 'oss' project always has an equivalent 'non-oss' project associated with it.''

'''I am a developer, where do I submit my changes to be included in the 1.2.1 release?'''

* MeeGo:1.2:oss:Testing.

'''I am a developer, where do I submit my changes to be included in the 1.2.0-Updates?'''

Before 1.2.1 is released, you need to submit your changes to ''both'' the 1.2 main branch project as well as the 1.2.0-Updates project.

So both:

* MeeGo:1.2:oss:Testing

* MeeGo:1.2.0:oss:Update:Testing

The reason is so that your change is also included in the future 1.2.1 release.

After 1.2.1 is released, you will submit your changes just to:

* MeeGo:1.2.0:oss:Update:Testing

'''I am a developer, where do I submit my changes to be included in the 1.2.1-Updates after 1.2.1 is released?'''

When 1.2.1 is released, there will be projects created called:

* MeeGo:1.2.1:oss:Update
* MeeGo:1.2.1:oss:Update:Testing

This is where you will submit those changes targeting 1.2.1-Update. If your change is also targeting 1.2.0-Update, you should also submit to that project as well (MeeGo:1.2.0:oss:Update:Testing).

'''Where can I get a quick reference list of repositories and OBS projects used for MeeGo?'''

* [[Release_Engineering/Repo_List|MeeGo Repository and OBS projects list]]

'''What kinds of changes are accepted into 1.2.0-Update?'''

Only bugs that are accepted as 1.2.0-Update blockers will be accepted into this project. Anyone can propose a bug to be an update blocker bug for 1.2.0, and Release Engineering with feedback from the CCB makes decisions on accepting/rejecting their status as blockers.

For more info on how this work, please go to this wiki:

* [[Release_Engineering/Release_Timeline/Branching_phase#Which_changes_are_accepted_into_Branch|Which changes are accepted into a Branch]]

''' What kinds of changes are accepted for the 1.2.1 release?'''

Only bugs that are accepted as 1.2 blockers will be accepted into this project. Anyone can propose a bug to be a blocker bug for 1.2, and Release Engineering with feedback from the CCB makes decisions on accepting/rejecting their status as blockers.

For more info on how this work, please go to this wiki:

* [[Release_Engineering/Release_Timeline/Branching_phase#Which_changes_are_accepted_into_Branch|Which changes are accepted into a Branch]]

== MeeGo 1.2.0/1.2.1 Bug Track Process ==

For MeeGo 1.2.0/1.2.1 bug track process, please refer to [http://wiki.meego.com/Quality/How_To_Report_Bugs#1.2.0.2F1.2.1_Bug_Tracking_Process 1.2.0/1.2.1 bug track process]

== MeeGo 1.2 Release Plan by Date ==

{| cellpadding="5" cellspacing="0" border="1"
! Iteration !! Iteration<br/>Start -- End<br/>Dates !! MeeGo Release Focus !! Status<br/>URL !! Features<br/>Bugfixes<br/>
|-
| style="background-color:#ff9900" | 1.1.80.0
| 2010-09-30 -- 2010-10-06
| MM1: Trunk opened for 1.2 development on 2010-09-30.
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.0.20101005.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.0|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.1
| 2010-10-07 -- 2010-10-13
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.1.20101012.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.1|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.2
| 2010-10-14 -- 2010-10-20
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.2.20101019.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.2|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.3
| 2010-10-21 -- 2010-10-27
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.3.20101026.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.3|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.4
| 2010-10-28 -- 2010-11-03
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.4.20101102.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.4|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.5
| 2010-11-04 -- 2010-11-10
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.5.20101109.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.5|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.6
| 2010-11-11 -- 2010-11-17
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.6.20101116.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.6|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.7
| 2010-11-18 -- 2010-11-24
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.7.20101123.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.7|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.8
| 2010-11-25 -- 2010-12-01
| MM2: Most intrusive changes delivered. Normal feature development continues after 2010-12-01. i18n code scans begin.
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.8.20101130.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.8|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.9
| 2010-12-02 -- 2010-12-08
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.9.20101207.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.9|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.10
| 2010-12-09 -- 2010-12-15
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.10.20101214.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.10|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.11
| 2010-12-16 -- 2010-12-22
| MM2.5: checkpoint for features delivery
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.11.20101221.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.11|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.12
| 2010-12-23 -- 2010-12-29
| Due to holidays in most of the countries, release has been skipped
|Skipped
| [[Release_Engineering/Plans/1.2/1.1.80.12|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.13
| 2010-12-30 -- 2011-01-05
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.13|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.14
| 2011-01-06 -- 2011-01-12
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.14.20110111.8/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.14|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.15
| 2011-01-13 -- 2011-01-19
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.15.20110118.5/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.15|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.0
| 2011-01-20 -- 2011-01-26
| MM3: All planned features released, Bugfixing for most of features starts after 2011-01-26, Possibility to integrate features that are late
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.90.0.20110125.3/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.0|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.1
| 2011-01-27 -- 2011-02-02
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.90/1.1.90.1.20110201.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.1|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.2
| 2011-02-03 -- 2011-02-09
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.2.20110208.4/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.2|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.3
| 2011-02-10 -- 2011-02-16
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.3.20110215.10/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.3|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.4
| 2011-02-17 -- 2011-02-23
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.4.20110222.2/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.4|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.5
| 2011-02-24 -- 2011-03-02
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.5.20110301.7/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.5|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.6
| 2011-03-03 -- 2011-03-09
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.6.20110308.5/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.6|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.7
| 2011-03-10 -- 2011-03-16
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.7.20110315.10/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.7|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.8
| 2011-03-17 -- 2011-03-23
|
|Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.90.8.20110322.2/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.8|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.0
| 2011-03-24 -- 2011-03-30
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110329.5/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.0|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.1
| 2011-03-31 -- 2011-04-06
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.1.20110405.3/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.1|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.2
| 2011-04-07 -- 2011-04-13
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.2.20110412.6/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.2|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.3
| 2011-04-14 -- 2011-04-20
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.3.20110419.9/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.3|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.4
| 2011-04-21 -- 2011-04-27
| MeeGo 1.2.0 Initial pre-release image available (4-26)
| Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.4.20110426.4/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.4|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.5
| 2011-04-28 -- 2011-05-04
| MeeGo 1.2.0 Branching from 1.2 (4-29)
|
| [[Release_Engineering/Plans/1.2/1.1.99.5|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.6
| 2011-05-05 -- 2011-05-11
| MeeGo 1.2.0 Final release candidate (5-6), MeeGo 1.2.0 Signed Gold image (5-10)
|
| [[Release_Engineering/Plans/1.2/1.1.99.6|Details]]
|-
| style="background-color:#339966" | 1.1.99.7
| 2011-05-12 -- 2011-05-18
|
|
| [[Release_Engineering/Plans/1.2/1.1.99.7|Details]]
|-
| style="background-color:#339966" | 1.2.0.0
| 2011-05-19 -- 2011-05-25
| MeeGo 1.2.0 Release Day (5-19)
|
| [[Release_Engineering/Plans/1.2/1.2.0.0|Details]]
|-
| style="background-color:#99cc00" | 1.2.0.90.0
| 2011-05-12 -- 2011-05-18
| Only 'accepted' 1.2 and 1.2 Update blocker bugs will be accepted from here on until 1.2.1 release.
|Released<br/>[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.0.20110517.1/ download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.1
| 2011-05-19 -- 2011-05-25
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.1.20110525.2/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.2
| 2011-06-09 -- 2011-06-15
| String Freeze (June 15)
|Skipped
|
|-
| style="background-color:#99cc00" | 1.2.0.90.3
| 2011-06-02 -- 2011-06-08
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.3.20110607.2/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.4
| 2011-06-09 -- 2011-06-15
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.4.20110614.1/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.5
| 2011-06-16 -- 2011-06-22
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.5.20110621.5/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.6
| 2011-06-23 -- 2011-06-29
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.7
| 2011-06-30 -- 2011-07-06
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.8
| 2011-07-07 -- 2011-07-13
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.9
| 2011-07-14 -- 2011-07-20
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.10
| 2011-07-21 -- 2011-07-27
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.11
| 2011-08-04 -- 2011-08-10
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.12
| 2011-08-11 -- 2011-08-17
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.13
| 2011-08-18 -- 2011-08-24
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.10
| 2011-08-25 -- 2011-08-31
|
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.0
| 2011-09-01 -- 2011-09-07
| Start stabilization phase towards release.
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.1
| 2011-09-08 -- 2011-09-14
|
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.2
| 2011-09-15 -- 2011-09-21
|
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.3
| 2011-09-22 -- 2011-09-28
|
|
|
|-
| style="background-color:#339966" | 1.2.0.99.4
| 2011-09-29 -- 2011-10-05
|
|
|
|-
| style="background-color:#339966" | 1.2.1
| 2011-10-06 -- 2011-10-11
| MeeGo 1.2.1 Release Day (Tablet images & MeeGo repos)
|
|
|}

== MeeGo 1.2 Features Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo Core OS Features,MeeGo Handset Features,MeeGo Netbook Features,MeeGo IVI Features
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Features&product=MeeGo+Connected+TV+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&product=MeeGo+IVI+Features&product=MeeGo+Netbook+Features&product=MeeGo+Tablet+Features&version=1.2&bug_severity=enhancement&format=table&action=wrap Detailed report in Featurezilla]

== MeeGo 1.2 Bugs Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo SDK,OS Base,OS Middleware,Handset User Experience,Netbook User Experience,Netbook IVI Experience
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Platform&product=Automotive+User+Experience&product=Handset+User+Experience&product=MeeGo+SDK&product=Netbook+User+Experience&product=OS+Base&product=OS+Middleware&version=1.2&format=table&action=wrap Detailed report in Bugzilla]

[[Category:Release engineering]]
[[Category:Meego-1.2]]

Release Engineering/Plans/1.2

2011-07-28T19:32:18Z

Uhofemeier:

== MeeGo 1.2 Release Plan (1.2.0, 1.2.1) ==

[[File:MeeGoReleaseTimeline1.2.x.jpg]]

=== Detailed summary ===

1.2.0 will be branched on May-01-2011 and released on May-19-2011.

1.2 will keep moving forward towards the 1.2.1 release.

1.2.0-Updates will be cherry-picked by the Meego Update team from the 1.2 Branch into 1.2.0.Updates.

1.2.1 will be branched around Aug-10-2011 and released around Sep-01-2011. The release will include the MeeGo Repos and Tablet 1.2.1 images.

1.2.1-Updates will then be cherry-picked by the Meego Update team from the 1.3 Branch into 1.2.1.Updates. At this point, 1.2.0.Updates will also be cherry-picked by the Meego update team.

1.2.1 will be the end of the 1.2-based releases.

=== FAQ ===

''Note: for all responses below, any 'oss' project always has an equivalent 'non-oss' project associated with it.''

'''I am a developer, where do I submit my changes to be included in the 1.2.1 release?'''

* MeeGo:1.2:oss:Testing.

'''I am a developer, where do I submit my changes to be included in the 1.2.0-Updates?'''

Before 1.2.1 is released, you need to submit your changes to ''both'' the 1.2 main branch project as well as the 1.2.0-Updates project.

So both:

* MeeGo:1.2:oss:Testing

* MeeGo:1.2.0:oss:Update:Testing

The reason is so that your change is also included in the future 1.2.1 release.

After 1.2.1 is released, you will submit your changes just to:

* MeeGo:1.2.0:oss:Update:Testing

'''I am a developer, where do I submit my changes to be included in the 1.2.1-Updates after 1.2.1 is released?'''

When 1.2.1 is released, there will be projects created called:

* MeeGo:1.2.1:oss:Update
* MeeGo:1.2.1:oss:Update:Testing

This is where you will submit those changes targeting 1.2.1-Update. If your change is also targeting 1.2.0-Update, you should also submit to that project as well (MeeGo:1.2.0:oss:Update:Testing).

'''Where can I get a quick reference list of repositories and OBS projects used for MeeGo?'''

* [[Release_Engineering/Repo_List|MeeGo Repository and OBS projects list]]

'''What kinds of changes are accepted into 1.2.0-Update?'''

Only bugs that are accepted as 1.2.0-Update blockers will be accepted into this project. Anyone can propose a bug to be an update blocker bug for 1.2.0, and Release Engineering with feedback from the CCB makes decisions on accepting/rejecting their status as blockers.

For more info on how this work, please go to this wiki:

* [[Release_Engineering/Release_Timeline/Branching_phase#Which_changes_are_accepted_into_Branch|Which changes are accepted into a Branch]]

''' What kinds of changes are accepted for the 1.2.1 release?'''

Only bugs that are accepted as 1.2 blockers will be accepted into this project. Anyone can propose a bug to be a blocker bug for 1.2, and Release Engineering with feedback from the CCB makes decisions on accepting/rejecting their status as blockers.

For more info on how this work, please go to this wiki:

* [[Release_Engineering/Release_Timeline/Branching_phase#Which_changes_are_accepted_into_Branch|Which changes are accepted into a Branch]]

== MeeGo 1.2.0/1.2.1 Bug Track Process ==

For MeeGo 1.2.0/1.2.1 bug track process, please refer to [http://wiki.meego.com/Quality/How_To_Report_Bugs#1.2.0.2F1.2.1_Bug_Tracking_Process 1.2.0/1.2.1 bug track process]

== MeeGo 1.2 Release Plan by Date ==

{| cellpadding="5" cellspacing="0" border="1"
! Iteration !! Iteration<br/>Start -- End<br/>Dates !! MeeGo Release Focus !! Status<br/>URL !! Features<br/>Bugfixes<br/>
|-
| style="background-color:#ff9900" | 1.1.80.0
| 2010-09-30 -- 2010-10-06
| MM1: Trunk opened for 1.2 development on 2010-09-30.
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.0.20101005.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.0|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.1
| 2010-10-07 -- 2010-10-13
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.1.20101012.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.1|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.2
| 2010-10-14 -- 2010-10-20
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.2.20101019.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.2|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.3
| 2010-10-21 -- 2010-10-27
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.3.20101026.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.3|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.4
| 2010-10-28 -- 2010-11-03
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.4.20101102.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.4|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.5
| 2010-11-04 -- 2010-11-10
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.5.20101109.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.5|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.6
| 2010-11-11 -- 2010-11-17
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.6.20101116.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.6|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.7
| 2010-11-18 -- 2010-11-24
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.7.20101123.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.7|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.8
| 2010-11-25 -- 2010-12-01
| MM2: Most intrusive changes delivered. Normal feature development continues after 2010-12-01. i18n code scans begin.
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.8.20101130.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.8|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.9
| 2010-12-02 -- 2010-12-08
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.9.20101207.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.9|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.10
| 2010-12-09 -- 2010-12-15
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.10.20101214.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.10|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.11
| 2010-12-16 -- 2010-12-22
| MM2.5: checkpoint for features delivery
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.11.20101221.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.11|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.12
| 2010-12-23 -- 2010-12-29
| Due to holidays in most of the countries, release has been skipped
|Skipped
| [[Release_Engineering/Plans/1.2/1.1.80.12|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.13
| 2010-12-30 -- 2011-01-05
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.13|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.14
| 2011-01-06 -- 2011-01-12
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.14.20110111.8/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.14|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.15
| 2011-01-13 -- 2011-01-19
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.80.15.20110118.5/ Download]
| [[Release_Engineering/Plans/1.2/1.1.80.15|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.0
| 2011-01-20 -- 2011-01-26
| MM3: All planned features released, Bugfixing for most of features starts after 2011-01-26, Possibility to integrate features that are late
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.80/1.1.90.0.20110125.3/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.0|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.1
| 2011-01-27 -- 2011-02-02
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/1.1.90/1.1.90.1.20110201.1/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.1|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.2
| 2011-02-03 -- 2011-02-09
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.2.20110208.4/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.2|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.3
| 2011-02-10 -- 2011-02-16
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.3.20110215.10/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.3|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.4
| 2011-02-17 -- 2011-02-23
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.4.20110222.2/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.4|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.5
| 2011-02-24 -- 2011-03-02
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.5.20110301.7/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.5|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.6
| 2011-03-03 -- 2011-03-09
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.6.20110308.5/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.6|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.7
| 2011-03-10 -- 2011-03-16
|
|Released<br/>[http://archive.meego.com/MeeGo/builds/trunk/1.1.90.7.20110315.10/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.7|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.8
| 2011-03-17 -- 2011-03-23
|
|Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.90.8.20110322.2/ Download]
| [[Release_Engineering/Plans/1.2/1.1.90.8|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.0
| 2011-03-24 -- 2011-03-30
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.0.20110329.5/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.0|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.1
| 2011-03-31 -- 2011-04-06
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.1.20110405.3/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.1|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.2
| 2011-04-07 -- 2011-04-13
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.2.20110412.6/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.2|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.3
| 2011-04-14 -- 2011-04-20
|
| |Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.3.20110419.9/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.3|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.4
| 2011-04-21 -- 2011-04-27
| MeeGo 1.2.0 Initial pre-release image available (4-26)
| Released<br/>[http://repo.meego.com/MeeGo/builds/trunk/1.1.99.4.20110426.4/ Download]
| [[Release_Engineering/Plans/1.2/1.1.99.4|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.5
| 2011-04-28 -- 2011-05-04
| MeeGo 1.2.0 Branching from 1.2 (4-29)
|
| [[Release_Engineering/Plans/1.2/1.1.99.5|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.6
| 2011-05-05 -- 2011-05-11
| MeeGo 1.2.0 Final release candidate (5-6), MeeGo 1.2.0 Signed Gold image (5-10)
|
| [[Release_Engineering/Plans/1.2/1.1.99.6|Details]]
|-
| style="background-color:#339966" | 1.1.99.7
| 2011-05-12 -- 2011-05-18
|
|
| [[Release_Engineering/Plans/1.2/1.1.99.7|Details]]
|-
| style="background-color:#339966" | 1.2.0.0
| 2011-05-19 -- 2011-05-25
| MeeGo 1.2.0 Release Day (5-19)
|
| [[Release_Engineering/Plans/1.2/1.2.0.0|Details]]
|-
| style="background-color:#99cc00" | 1.2.0.90.0
| 2011-05-12 -- 2011-05-18
| Only 'accepted' 1.2 and 1.2 Update blocker bugs will be accepted from here on until 1.2.1 release.
|Released<br/>[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.0.20110517.1/ download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.1
| 2011-05-19 -- 2011-05-25
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.1.20110525.2/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.2
| 2011-06-09 -- 2011-06-15
| String Freeze (June 15)
|Skipped
|
|-
| style="background-color:#99cc00" | 1.2.0.90.3
| 2011-06-02 -- 2011-06-08
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.3.20110607.2/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.4
| 2011-06-09 -- 2011-06-15
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.4.20110614.1/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.5
| 2011-06-16 -- 2011-06-22
|
|Released<br/>
[http://repo.meego.com/MeeGo/builds/1.2.0.90/1.2.0.90.5.20110621.5/ Download]
|
|-
| style="background-color:#99cc00" | 1.2.0.90.6
| 2011-06-23 -- 2011-06-29
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.7
| 2011-06-30 -- 2011-07-06
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.8
| 2011-07-07 -- 2011-07-13
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.9
| 2011-07-14 -- 2011-07-20
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.10
| 2011-07-21 -- 2011-07-27
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.11
| 2011-08-04 -- 2011-08-10
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.12
| 2011-08-11 -- 2011-08-17
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.13
| 2011-08-18 -- 2011-08-24
|
|
|
|-
| style="background-color:#99cc00" | 1.2.0.90.10
| 2011-08-25 -- 2011-08-31
|
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.0
| 2011-07-28 -- 2011-08-03
| Start stabilization phase towards release.
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.1
| 2011-08-04 -- 2011-08-10
|
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.2
| 2011-08-11 -- 2011-08-17
|
|
|
|-
| style="background-color:#00ff00" | 1.2.0.99.3
| 2011-08-18 -- 2011-08-24
|
|
|
|-
| style="background-color:#339966" | 1.2.0.99.4
| 2011-08-25 -- 2011-08-31
|
|
|
|-
| style="background-color:#339966" | 1.2.1
| 2011-09-01 -- 2011-09-07
| MeeGo 1.2.1 Release Day (Tablet images & MeeGo repos)
|
|
|}

== MeeGo 1.2 Features Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo Core OS Features,MeeGo Handset Features,MeeGo Netbook Features,MeeGo IVI Features
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Features&product=MeeGo+Connected+TV+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&product=MeeGo+IVI+Features&product=MeeGo+Netbook+Features&product=MeeGo+Tablet+Features&version=1.2&bug_severity=enhancement&format=table&action=wrap Detailed report in Featurezilla]

== MeeGo 1.2 Bugs Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo SDK,OS Base,OS Middleware,Handset User Experience,Netbook User Experience,Netbook IVI Experience
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Platform&product=Automotive+User+Experience&product=Handset+User+Experience&product=MeeGo+SDK&product=Netbook+User+Experience&product=OS+Base&product=OS+Middleware&version=1.2&format=table&action=wrap Detailed report in Bugzilla]

[[Category:Release engineering]]
[[Category:Meego-1.2]]

Build Infrastructure

2011-07-01T15:52:51Z

Uhofemeier:

== MeeGo Build Infrastructure ==

The heart of the Build Infrastructure of MeeGo is the upstream project [http://wiki.opensuse.org/Portal:Build_Service openSUSE Build Service (OBS)]. It is an automated system used for building software packages, collaboration of developers, release management, maintenance, and much more. Moblin started using OBS in June 2008 and released Moblin 2.0 and Moblin 2.1, as well as other derivative releases. OBS has proven to be a very reliable, quickly evolving infrastructure. It is rich with distribution building and maintenance features. The Linux Foundation is dedicated to the further development of OBS and has a team, including two full-time OBS maintainers, contributing to its development and its use by MeeGo and the Ecosystem.

MeeGo currently uses OBS version 2.1.6. To learn more about version 2.1 and the additional features in it, see the upstream project details: [http://wiki.opensuse.org/openSUSE:Build_Service_Roadmap roadmap].

There are 2 build system instances that are relevant to MeeGo:
* MeeGo build system: Essentially, if you're a package maintainer/developer which is part of MeeGo, you get an account here.
* MeeGo public build system (AKA community OBS): For anyone to build applications or libraries against MeeGo. Anyone with a meego.com account can use this.

=== Overview - What does it do? ===
Let's set out some basics about the OBS.

# It's a build system. You put source on it and say "use this repository" and it builds a minimal SDK-like chroot using the deb/rpms it finds in that repository
# It has packages - a package corresponds to a tarball and a spec/dsc
# It has projects - a project is like a directory with packages
# When a package is built it is "published" from the project where it was uploaded into a corresponding repository (which can be used to build other projects)
# The repositories can also be used by devices to download binary packages.

[[File:Splash-community.png|right|300px]]
===MeeGo Build Service ===
The [http://build.meego.com MeeGo build system] is part of meego.com infrastructure and supports several important kinds of development:

* Applications to run on MeeGo
* Team Repositories
* Personal Repositories

Having these areas allow us to support:
* Managing packages as part of their acceptance into MeeGo core
* Deprecating packages from MeeGo core

=== MeeGo Community Build Service OBS ===
There's also a [[Build_Infrastructure/Community_Builder|MeeGo Build Service]] available.

=== [[Build_Infrastructure/Packagers_Developers|Packagers/Developers]] ===
* [[Build_Infrastructure/Packagers_Developers#How_to_get_started|How to get started.]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_webinterface|How to use the web interface to view, manage and build your packages.]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers#MeeGo_Packaging_guidelines_and_Howto|MeeGo Packaging guidelines and howto]]
* [[Build_Infrastructure/Packagers_Developers#QA_Processes_around_the_OBS|QA Processes around the OBS]]
* [[Build_Infrastructure/Packagers_Developers#Multi-Architecture_and_Multi-Distribution_packaging|Multi-Architecture and Multi-Distribution packaging]]
* [[Build_Infrastructure/Packagers_Developers#Tips_.26_Tricks|Verifying Your Package Changes Locally and Online]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

[[File:peep_skate.png|right]]

=== [[Build_Infrastructure/Developing_OBS|Developing for the openSUSE Build Service]] ===
* [http://en.opensuse.org/openSUSE:Build_Service_private_instance How to set up a Build Service locally for testing]
* [[Build_Infrastructure/Sysadmin_Distro|More on setting up an OBS server]]
** [[Build_Infrastructure/Sysadmin_Distro#Seamless_cross-compilation.2C_cross-toolchain_integration|Seamless cross-compilation, cross-toolchain integration]]
* What's the [http://en.opensuse.org/openSUSE:Build_Service_Tutorial#Create_Patterns metadata (prjconf/prj), attributes, admin-tools for?]

[[File:peep_netbook.png|right]]

[[Category:Build Infrastructure]]

Build Infrastructure

2011-07-01T15:52:02Z

Uhofemeier:

== MeeGo Build Infrastructure ==

The heart of the Build Infrastructure of MeeGo is the upstream project [http://wiki.opensuse.org/Portal:Build_Service openSUSE Build Service (OBS)]. It is an automated system used for building software packages, collaboration of developers, release management, maintenance, and much more. Moblin started using OBS in June 2008 and released Moblin 2.0 and Moblin 2.1, as well as other derivative releases. OBS has proven to be a very reliable, quickly evolving infrastructure. It is rich with distribution building and maintenance features. The Linux Foundation is dedicated to the further development of OBS and has a team, including two full-time OBS maintainers, contributing to its development and its use by MeeGo and the Ecosystem.

MeeGo currently uses OBS version 2.1.6. To learn more about version 2.1 and the additional features in it, see the upstream project details: [http://wiki.opensuse.org/openSUSE:Build_Service_Roadmap roadmap].

There are 2 build system instances that are relevant to MeeGo:
* MeeGo build system: Essentially, if you're a package maintainer/developer which is part of MeeGo, you get an account here.
* MeeGo public build system (AKA community OBS): For anyone to build applications or libraries against MeeGo. Anyone with a meego.com account can use this.

=== Overview - What does it do? ===
Let's set out some basics about the OBS.

# It's a build system. You put source on it and say "use this repository" and it builds a minimal SDK-like chroot using the deb/rpms it finds in that repository
# It has packages - a package corresponds to a tarball and a spec/dsc
# It has projects - a project is like a directory with packages
# When a package is built it is "published" from the project where it was uploaded into a corresponding repository (which can be used to build other projects)
# The repositories can also be used by devices to download binary packages.

[[File:Splash-community.png|right|300px]]
===MeeGo Build System ===
The [http://build.meego.com MeeGo build system] is part of meego.com infrastructure and supports several important kinds of development:

* Applications to run on MeeGo
* Team Repositories
* Personal Repositories

Having these areas allow us to support:
* Managing packages as part of their acceptance into MeeGo core
* Deprecating packages from MeeGo core

=== MeeGo Build Service OBS ===
There's also a [[Build_Infrastructure/Community_Builder|MeeGo Build Service]] available.

=== [[Build_Infrastructure/Packagers_Developers|Packagers/Developers]] ===
* [[Build_Infrastructure/Packagers_Developers#How_to_get_started|How to get started.]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_webinterface|How to use the web interface to view, manage and build your packages.]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers#MeeGo_Packaging_guidelines_and_Howto|MeeGo Packaging guidelines and howto]]
* [[Build_Infrastructure/Packagers_Developers#QA_Processes_around_the_OBS|QA Processes around the OBS]]
* [[Build_Infrastructure/Packagers_Developers#Multi-Architecture_and_Multi-Distribution_packaging|Multi-Architecture and Multi-Distribution packaging]]
* [[Build_Infrastructure/Packagers_Developers#Tips_.26_Tricks|Verifying Your Package Changes Locally and Online]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

[[File:peep_skate.png|right]]

=== [[Build_Infrastructure/Developing_OBS|Developing for the openSUSE Build Service]] ===
* [http://en.opensuse.org/openSUSE:Build_Service_private_instance How to set up a Build Service locally for testing]
* [[Build_Infrastructure/Sysadmin_Distro|More on setting up an OBS server]]
** [[Build_Infrastructure/Sysadmin_Distro#Seamless_cross-compilation.2C_cross-toolchain_integration|Seamless cross-compilation, cross-toolchain integration]]
* What's the [http://en.opensuse.org/openSUSE:Build_Service_Tutorial#Create_Patterns metadata (prjconf/prj), attributes, admin-tools for?]

[[File:peep_netbook.png|right]]

[[Category:Build Infrastructure]]

Build Infrastructure/Packagers Developers

2011-06-28T23:20:10Z

Uhofemeier:

These pages are in preparation - contributions welcome.

Note: See [[OBS|the OBS wiki page]] for explanation of the different OBS services MeeGo offers.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.
Note: You need an account to access build.meego.com.
If you have no account, you can still learn how the OBS works at the upstream project's own instance [http://build.opensuse.org http://build.opensuse.org] .

In this track, you'll learn how to use the web interface, the commandline client and create your first package.
The packaging guidelines and more advanced topics are also covered.

== How to get started ==

You need an account on build.meego.com. To request an account:
# Go to [http://bugs.meego.com MeeGo bugzilla].
# Click New in the upper navigational bar to begin filing a bug.
# On the next page, click MeeGo Community Infrastructure.
# On the following page, click Build Service and file your bug.

== How to use the web interface ==
A series of pages will make you familiar with webinterface basics. It's divided into several subpages:
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
* [[Developing_in_a_MeeGo_Environment#Building_your_package:_Step_by_step|Part 3 - Your first own package]]

== How to use the commandline client ==
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout of projects, commit]]
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|branch packages to home project]]
* part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

== MeeGo Packaging guidelines and Howto ==
* [[Packaging|Packaging]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Packaging Tutorial]]

== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
See the [[Quality]] page.

== Verifying Your Package Changes Locally and Online ==
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]

== Troubleshooting ==

* '''I'm getting "error: Package already exists: %package debuginfo"''' — Disable the debuginfo flag for the repo/arch that gives you this problem. You will probably still get a debuginfo package. This appears to happen when OBS creates debuginfo packages by default, and so this flag causes a sort of doubling-up of the debuginfo package.

== IRC / mailinglists / contact ==

If you need help, you can join #meego on irc.freenode.net . See also [[Community communication|this page]] about all MeeGo IRC channels.

You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].

[[Category:Build Infrastructure]]

Build Infrastructure/Packagers Developers

2011-06-28T23:18:59Z

Uhofemeier:

These pages are in preparation - contributions welcome.

Note: See [[OBS|the OBS wiki page]] for explanation of the different OBS services MeeGo offers.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.
Note: You need an account to access build.meego.com.
If you have no account, you can still learn how the OBS works at the upstream project's own instance [http://build.opensuse.org http://build.opensuse.org] .

In this track, you'll learn how to use the web interface, the commandline client and create your first package.
The packaging guidelines and more advanced topics are also covered.

== How to get started ==

You need an account on build.meego.com. To request an account:
# Go to [http://bugs.meego.com MeeGo bugzilla].
# Click New in the upper navigational bar to begin filing a bug.
# On the next page, click MeeGo Community Infrastructure.
# On the following page, click Build Service and file your bug.

== How to use the web interface ==
A series of pages will make you familiar with webinterface basics. It's divided into several subpages:
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
* [[Developing_in_a_MeeGo_Environment#Building_your_package:_Step_by_step|Part 3 - Your first own package]]

== How to use the commandline client ==
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout of projects, commit]]
* Part 3 - [http://wiki.meego.com/Build_Infrastructure/Packagers_Developers/CLI_Part_2]
* part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

== MeeGo Packaging guidelines and Howto ==
* [[Packaging|Packaging]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Packaging Tutorial]]

== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
See the [[Quality]] page.

== Verifying Your Package Changes Locally and Online ==
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]

== Troubleshooting ==

* '''I'm getting "error: Package already exists: %package debuginfo"''' — Disable the debuginfo flag for the repo/arch that gives you this problem. You will probably still get a debuginfo package. This appears to happen when OBS creates debuginfo packages by default, and so this flag causes a sort of doubling-up of the debuginfo package.

== IRC / mailinglists / contact ==

If you need help, you can join #meego on irc.freenode.net . See also [[Community communication|this page]] about all MeeGo IRC channels.

You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].

[[Category:Build Infrastructure]]

Release Engineering/Repo List

2011-06-07T22:03:17Z

Uhofemeier:

Repos to use when creating images.

== Build repos ==

=== Trunk repos and projects ===

Related OBS projects are:

- Trunk

- Trunk:non-oss

Daily snapshots

- [http://repo.meego.com/MeeGo/snapshots/stable/ Daily Trunk snapshots]

=== Trunk:Testing repos and projects ===

Related OBS projects are:

- Trunk:Testing

- Trunk:non-oss:Testing

Daily snapshots

- [http://repo.meego.com/MeeGo/snapshots/testing Daily Trunk:Testing snapshots]

=== MeeGo 1.2 repos and projects (targeting 1.2.1) ===

Related OBS projects are:

- MeeGo:1.2:oss

- MeeGo:1.2:non-oss

Daily snapshots:

- [http://repo.meego.com/MeeGo/snapshots/stable Daily MeeGo:1.2 snapshots]

=== MeeGo 1.2:Testing repos and projects (targeting 1.2.1) ===

Related OBS projects are:

- MeeGo:1.2:oss:Testing

- MeeGo:1.2:non-oss:Testing

Daily snapshots:

- [http://repo.meego.com/MeeGo/snapshots/testing Daily MeeGo:1.2:Testing snapshots]

=== MeeGo 1.2.0:oss:Update repo (MeeGo 1.2.0 Updates reside here) ===

Related OBS projects are:

- MeeGo:1.2.0:oss:Update

- MeeGo:1.2.0:non-oss:Update

== OBS MeeGo Build Targets ==

MeeGo Build Targets to use when building pkgs in MeeGo.

=== To Build against Trunk ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo Trunk'

This ensures that the pkgs in your project are building against the MeeGo Trunk repo.

=== To Build against Trunk:Testing ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo Trunk:Testing'

This ensures that the pkgs in your project are building against the MeeGo Trunk:Testing repo.

=== To Build against MeeGo 1.2 ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo 1.2'

This ensures that the pkgs in your project are building against the MeeGo Trunk repo.

=== To Build against MeeGo 1.2:Testing ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo 1.2 Testing'

This ensures that the pkgs in your project are building against the MeeGo Trunk:Testing repo.

[[Category:Release engineering]]

Release Engineering/Repo List

2011-06-07T22:02:48Z

Uhofemeier:

Release Engineering/Repo List

2011-06-07T22:02:16Z

Uhofemeier:

Repos to use when creating images.

== Build repos ==

=== Trunk repos and projects ===

Related OBS projects are:

- Trunk

- Trunk:non-oss

Daily snapshots

- [http://repo.meego.com/MeeGo/snapshots/stable/ Daily Trunk snapshots]

=== Trunk:Testing repos and projects ===

Related OBS projects are:

- Trunk:Testing

- Trunk:non-oss:Testing

Daily snapshots

- [http://repo.meego.com/MeeGo/snapshots/testing Daily Trunk:Testing snapshots]

=== MeeGo 1.2 repos and projects (targeting 1.2.1) ===

Related OBS projects are:

- MeeGo:1.2:oss

- MeeGo:1.2:non-oss

Daily snapshots:

- [http://repo.meego.com/MeeGo/snapshots/stable Daily MeeGo:1.2 snapshots]

=== MeeGo 1.2:Testing repos and projects (targeting 1.2.1) ===

Related OBS projects are:

- MeeGo:1.2:oss:Testing

- MeeGo:1.2:non-oss:Testing

Daily snapshots:

- [http://repo.meego.com/MeeGo/snapshots/testing Daily MeeGo:1.2:Testing snapshots]

=== MeeGo 1.2.0:oss:Update repo MeeGo 1.2.0 Updates reside here) ===

Related OBS projects are:

- MeeGo:1.2.0:oss:Update

- MeeGo:1.2.0:non-oss:Update

== OBS MeeGo Build Targets ==

MeeGo Build Targets to use when building pkgs in MeeGo.

=== To Build against Trunk ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo Trunk'

This ensures that the pkgs in your project are building against the MeeGo Trunk repo.

=== To Build against Trunk:Testing ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo Trunk:Testing'

This ensures that the pkgs in your project are building against the MeeGo Trunk:Testing repo.

=== To Build against MeeGo 1.2 ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo 1.2'

This ensures that the pkgs in your project are building against the MeeGo Trunk repo.

=== To Build against MeeGo 1.2:Testing ===

# Login to build.meego.com
# Go your project with the pkgs you want to build
# Click on the 'Repositories' tab
# Click on 'Add repositories'
# Check 'MeeGo 1.2 Testing'

This ensures that the pkgs in your project are building against the MeeGo Trunk:Testing repo.

[[Category:Release engineering]]

Release Engineering

2011-05-04T16:09:51Z

Uhofemeier:

The Release Engineering team manages planning and producing all the MeeGo releases, including the weekly engineering releases, milestone releases, and MeeGo product releases. The team maintains the process and tooling for organized and automated build and release creation and maintains hardware platform-specific software in MeeGo.

== Team ==

* '''[http://meego.com/users/rolla Rolla Selbak]''' is the MeeGo release engineering manager. She is responsible for the MeeGo release engineering process and code line policy, and for overseeing and supporting the planning and production of MeeGo releases.
* '''[http://meego.com/users/peter Peter Zhu]''' is the MeeGo Core OS release lead, responsible for planning and producing core OS releases.
* '''[http://meego.com/users/ulf Ulf Hofemeier]''' is the MeeGo Handset release lead, responsible for planning and producing handset releases.
* '''[http://meego.com/users/Praj Praj Karur Mohan]''' is the MeeGo Tablet release lead, responsible for planning and producing tablet releases.
* '''[http://meego.com/users/Tgraydon Tracy Graydon]''' is the MeeGo IVI release lead, responsible for planning and producing IVI releases.
* '''[http://meego.com/users/Yyin2 Yin Yan]''' is the MeeGo Netbook & TV release lead, responsible for planning and producing Netbook & TV releases.

== Terms and conventions ==

=== Supported CPU architectures ===
* '''ia32''' - 32bit [[wikipedia:Intel Atom|Intel Atom]], [[wikipedia:Intel Core 2|Intel Core 2]] or better CPU (support for [[wikipedia:SSSE3|SSSE3]] is required)
* '''armv7el''' - [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs (Cortex-A8, Thumb-2, NEON, VPFv3, [[wikipedia:Endianness|Little-endian]])
* '''armv8el''' (OBS scheduler name), '''armv7hl''' (RPM base architecture) [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs, with hard-float ABI (VFPv3-D16, subarchitectures exist for NEON and Thumb2)

== Build Infrastructure ==
* [[Build_Infrastructure|What does it do? How to request an account, etc.]]

=== Release Versioning ===
* [[Release_Engineering/Release_Versioning|MeeGo Release and Builds Versioning]]

== Release Process ==

* [[Release_Engineering/Release_Timeline|Release 6-month lifecycle timeline]]
* [[Release_Engineering/Process|MeeGo release process]]
* [[Release_Engineering/New_Package_Checklist|Checklist for new package submissions]]
* [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]]
* [[Release_Engineering/Repo_List|Repos to use for MeeGo]]
* [[Release_Engineering/Software_update_process|MeeGo Software update process]]

== Release Plans ==
* [[Release_Engineering/Plans/1.1|MeeGo 1.1 release planning]]
* [[Release_Engineering/Plans/1.2|MeeGo 1.2 release planning]]

== Downloads ==

* [http://repo.meego.com/MeeGo/releases/ MeeGo Official Releases]
* [http://repo.meego.com/MeeGo/updates/ MeeGo Updates]
* [http://repo.meego.com/MeeGo/builds/ MeeGo development releases]

[[Category:Release engineering]]

Release Engineering

2011-05-04T16:09:34Z

Uhofemeier:

Release Engineering

2011-05-04T16:07:57Z

Uhofemeier:

The Release Engineering team manages planning and producing all the MeeGo releases, including the weekly engineering releases, milestone releases, and MeeGo product releases. The team maintains the process and tooling for organized and automated build and release creation and maintains hardware platform-specific software in MeeGo.

== Team ==

* '''[http://meego.com/users/rolla Rolla Selbak]''' is the MeeGo release engineering manager. She is responsible for the MeeGo release engineering process and code line policy, and for overseeing and supporting the planning and production of MeeGo releases.
* '''[http://meego.com/users/peter Peter Zhu]''' is the MeeGo Core OS release lead, responsible for planning and producing core OS releases.
* '''[http://meego.com/users/ulf Ulf Hofemeier]''' is the MeeGo Handset release lead, responsible for planning and producing handset releases.
* '''[http://meego.com/users/Praj Praj Karur Mohan]''' is the MeeGo Tablet release lead, responsible for planning and producing tablet releases.
* '''[http://meego.com/users/Tgraydon Tracy Graydon]''' is the MeeGo IVI release lead, responsible for planning and producing IVI releases.
* '''[http://meego.com/users/Yyin2 Yin Yan]''' is the MeeGo Netbook & TV release lead, responsible for planning and producing Netbook & TV releases.

== Terms and conventions ==

=== Supported CPU architectures ===
* '''ia32''' - 32bit [[wikipedia:Intel Atom|Intel Atom]], [[wikipedia:Intel Core 2|Intel Core 2]] or better CPU (support for [[wikipedia:SSSE3|SSSE3]] is required)
* '''armv7el''' - [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs (Cortex-A8, Thumb-2, NEON, VPFv3, [[wikipedia:Endianness|Little-endian]])
* '''armv8el''' (OBS scheduler name), '''armv7hl''' (RPM base architecture) [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs, with hard-float ABI (VFPv3-D16, subarchitectures exist for NEON and Thumb2)

=== Build Infrastructure ===
* [[Build_Infrastructure|What does it do? How to request an account, etc.]]

=== Release Versioning ===
* [[Release_Engineering/Release_Versioning|MeeGo Release and Builds Versioning]]

== Release Process ==

* [[Release_Engineering/Release_Timeline|Release 6-month lifecycle timeline]]
* [[Release_Engineering/Process|MeeGo release process]]
* [[Release_Engineering/New_Package_Checklist|Checklist for new package submissions]]
* [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]]
* [[Release_Engineering/Repo_List|Repos to use for MeeGo]]
* [[Release_Engineering/Software_update_process|MeeGo Software update process]]

== Release Plans ==
* [[Release_Engineering/Plans/1.1|MeeGo 1.1 release planning]]
* [[Release_Engineering/Plans/1.2|MeeGo 1.2 release planning]]

== Downloads ==

* [http://repo.meego.com/MeeGo/releases/ MeeGo Official Releases]
* [http://repo.meego.com/MeeGo/updates/ MeeGo Updates]
* [http://repo.meego.com/MeeGo/builds/ MeeGo development releases]

[[Category:Release engineering]]

Release Engineering

2011-04-22T16:17:09Z

Uhofemeier:

The Release Engineering team manages planning and producing all the MeeGo releases, including the weekly engineering releases, milestone releases, and MeeGo product releases. The team maintains the process and tooling for organized and automated build and release creation and maintains hardware platform-specific software in MeeGo.

== Team ==

* '''[http://meego.com/users/rolla Rolla Selbak]''' is the MeeGo release engineering manager. She is responsible for the MeeGo release engineering process and code line policy, and for overseeing and supporting the planning and production of MeeGo releases.
* '''[http://meego.com/users/peter Peter Zhu]''' is the MeeGo Core OS release lead, responsible for planning and producing core OS releases.
* '''[http://meego.com/users/ulf Ulf Hofemeier]''' is the MeeGo Handset release lead, responsible for planning and producing handset releases.
* '''[http://meego.com/users/Praj Praj Karur Mohan]''' is the MeeGo Tablet release lead, responsible for planning and producing tablet releases.
* '''[http://meego.com/users/Tgraydon Tracy Graydon]''' is the MeeGo IVI release lead, responsible for planning and producing IVI releases.
* '''[http://meego.com/users/Yyin2 Yin Yan]''' is the MeeGo Netbook & TV release lead, responsible for planning and producing Netbook & TV releases.

== Terms and conventions ==

=== Supported CPU architectures ===
* '''ia32''' - 32bit [[wikipedia:Intel Atom|Intel Atom]], [[wikipedia:Intel Core 2|Intel Core 2]] or better CPU (support for [[wikipedia:SSSE3|SSSE3]] is required)
* '''armv7el''' - [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs (Cortex-A8, Thumb-2, NEON, VPFv3, [[wikipedia:Endianness|Little-endian]])
* '''armv8el''' (OBS scheduler name), '''armv7hl''' (RPM base architecture) [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs, with hard-float ABI (VFPv3-D16, subarchitectures exist for NEON and Thumb2)

=== Release Versioning ===
* [[Release_Engineering/Release_Versioning|MeeGo Release and Builds Versioning]]

== Release Process ==

* [[Release_Engineering/Release_Timeline|Release lifecycle timeline]]
* [[Release_Engineering/Process|MeeGo release process]]
* [[Release_Engineering/New_Package_Checklist|A 6-step checklist for package submissions]]
* [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]]
* [[Release_Engineering/Repo_List|Repos to use for MeeGo]]
* [[Release_Engineering/Software_update_process|MeeGo Software update process]]

== Release Plans ==
* [[Release_Engineering/Plans/1.1|MeeGo 1.1 release planning]]
* [[Release_Engineering/Plans/1.2|MeeGo 1.2 release planning]]

== Downloads ==

* [http://repo.meego.com/MeeGo/releases/ MeeGo Official Releases]
* [http://repo.meego.com/MeeGo/updates/ MeeGo Updates]
* [http://repo.meego.com/MeeGo/builds/ MeeGo development releases]

[[Category:Release engineering]]

Release Engineering/New Package Checklist

2011-04-21T22:07:17Z

Uhofemeier:

== New package checklist ==

This a checklist which developers have to follow to submit a new package to MeeGo OBS of http://build.meego.com. This checklist talks about only specical parts for new package, for other commen practise required to submit code to MeeGo, please follow [[Release_Engineering/Submission_Checklist|Submission Checklist]]

Following this checklist will ensure smooth submission and acceptance of NEW package.

=== Step 1: Have your Program Manager provide you with an SBOM (Software Bill of Materials.) ===
An SBOM is required to be completed by the P.M and submitted to the Release Engineering team when packages for specific verticals/products are going to be introduced into MeeGo.

=== Step 2: Agreed upon by copyright owner ===

Please make sure copyright owner of this new package agree putting it in public MeeGo OBS of http://build.meego.com. Especially if it's owned by a company, we need to be more careful.
* For package owned by Intel, please make sure it passes open source PDT.
* If this package is from community
** Talks to maintainer via project mailing list to ask for permission
** If first approach is unavailable, please make sure it is in at least two other linux distributions

=== Step 3: Appropriate license ===

Please make sure appropriate license is attached to this new package. Specially MeeGo doesn't allow a package of GPLV3 into default build of non-netbook image. So make sure it doesn't need to be installed by default if it's GPLV3. Otherwise, if this new package is GPLV3 and/or has dependency of another GPLV3 package, you either stop here or you could do following to move further
* Remove GPLv3 parts or parts requires another GPLV3 package OR
* Rewrite GPLv3 parts by yourself so that this package doens't need to be GPLV3 OR
* Revert back to a non-GPLV3 version

=== Step 4: It must be with a FEA# ===

Make sure this new package is with a feature. If there is no FEA# for the package, file one by yourself and get it approved by Program Manager

=== Step 5: Submit to correct target project ===

Depends on what this new package for and desire of copyright owner for that package, you might choose to submit different project

* Trunk:Testing which is staging project for Trunk for all of open sourced packages
* Trunk:non-oss:Testing which staging project for Trunk:non-oss for all those packages MeeGo could redistribute but copyright owner(s) don't want to get them open-sourced like some 3D gfx packages and phone call specific packages.

=== Step 6: Claim ownership ===
Once your package are accepted, please claim ownership for this package use "osc reqms --role bugowner". For detail, please reference of [[Packaging/Guidelines#Maintaining_a_Package|Maintain a package]]

[[Category:Release engineering]]

Release Engineering/New Package Checklist

2011-04-21T20:47:19Z

Uhofemeier:

== New package checklist ==

This a checklist which developers have to follow to submit a new package to MeeGo OBS of http://build.meego.com. This checklist talks about only specical parts for new package, for other commen practise required to submit code to MeeGo, please follow [[Release_Engineering/Submission_Checklist|Submission Checklist]]

Following this checklist will ensure smooth submission and acceptance of NEW package.

=== Step 1: Have your Program Manager provide you with an SBOM (Software Bill of Materials.) ===
An SBOM is required to be completed by the P.M and submitted to the Release Engineering team when packages for specific verticals/products are going to be introduced into MeeGo.

=== Step 2: Agreed upon by copyright owner ===

Please make sure copyright owner of this new package agree putting it in public MeeGo OBS of http://build.meego.com. Especially if it's owned by a company, we need to be more careful.
* For package owned by Intel, please make sure it passes open source PDT. Nokia has similar process inside.
* If this package is from community
** Talks to maintainer via project mailing list to ask for permission
** If first approach is unavailable, please make sure it is in at least two other linux distributions

=== Step 3: Appropriate license ===

Please make sure appropriate license is attached to this new package. Specially MeeGo doesn't allow a package of GPLV3 into default build of non-netbook image. So make sure it doesn't need to be installed by default if it's GPLV3. Otherwise, if this new package is GPLV3 and/or has dependency of another GPLV3 package, you either stop here or you could do following to move further
* Remove GPLv3 parts or parts requires another GPLV3 package OR
* Rewrite GPLv3 parts by yourself so that this package doens't need to be GPLV3 OR
* Revert back to a non-GPLV3 version

=== Step 4: It must be with a FEA# ===

Make sure this new package is with a feature. If there is no FEA# for the package, file one by yourself and get it approved by Program Manager

=== Step 5: Submit to correct target project ===

Depends on what this new package for and desire of copyright owner for that package, you might choose to submit different project

* Trunk:Testing which is staging project for Trunk for all of open sourced packages
* Trunk:non-oss:Testing which staging project for Trunk:non-oss for all those packages MeeGo could redistribute but copyright owner(s) don't want to get them open-sourced like some 3D gfx packages and phone call specific packages.

=== Step 6: Claim ownership ===
Once your package are accepted, please claim ownership for this package use "osc reqms --role bugowner". For detail, please reference of [[Packaging/Guidelines#Maintaining_a_Package|Maintain a package]]

[[Category:Release engineering]]

Build Infrastructure/Packagers Developers/Using OBS chroot for development

2011-04-18T15:41:12Z

Uhofemeier:

In OBS, you can build packages both in the OBS server (build.meego.com),
or do a local build.

When you do an OBS local build for a package, OBS creates a local chroot under /var/tmp/build-root.
OBS first prepares the chroot by installing dependant packages from the OBS server inside the chroot
(that is, IF they are found in the OBS repository you're building against). After that, it takes your
tarball, spec (and possible patches), builds things inside chroot and gives you a new RPM package.

== Doing a local build with OBS ==

'''First get a new package to your home project by using one of these:'''

'''1. Copying/linking a package which exists in the OBS server'''
- osc copypac/linkpac <repository>/<package> home:myusername
- osc co home:myusername/<package>

'''2. Creating a new package'''

- create new package in OBS web UI OR 'osc meta pkg -e home:myusername <mypackage>'
- osc co home:myusername/<mypackage>
- Add the spec file, tarball, patches to the project and you're ready to build.

If you have a source RPM that you want to rebuild, extract it with '''rpm2cpio <the.src.rpm> | cpio -idmv''' and you get the spec file, tarball and possible patches.

Local build command: '''osc build <options> <repository> <target architecture>''' (see 'osc help build' for details)

== Using the OBS chroot for development ==
This assumes that the package dependencies have been solved and the package has been succesfully built using the local build. Let's say you have built a package called '''mypackage.rpm'''. This means that the chroot now contains all the dependencies and tools needed to develop that package. (The instructions below assume your distro is using sudo, adjust the commands accordingly if you're not using e.g. Ubuntu)

'''Rebuilding the sources inside OBS chroot'''
- Make a directory for the package: sudo mkdir /var/tmp/build-root/home/abuild/mypackage
- Copy/untar the sources under the directory above
- Move to the chroot: sudo chroot /var/tmp/build-root
- cd /home/abuild/mypackage
- Develop the code normally
- call configure & make and whatever is needed to build your package
- 'exit' when you're done working inside the chroot

'''Repackaging the code that was developed inside the chroot'''
- sudo tar -czf mypackage.tar /var/tmp/build-root/home/abuild/mypackage
- copy the tarball into your OBS project which contains the previously packaged version
- adjust mypackage.spec to use the tarball and possible dependency/file changes etc
- osc build <options> <repository> <target architecture>

Packaging

2011-04-18T15:10:32Z

Uhofemeier:

This page needs re-writing

It should outline MeeGo policy in the areas of packaging and should link to support pages covering reference and tutorial material.
Don't forget that readers will come from other rpm distros and from deb distros too.

== Creating Packages for MeeGo ==

* The package format used by MeeGo is [[:wikipedia:RPM Package Manager|RPM]]. If you are a packager and used to DEB packages, see [[Packaging/Deb conversion example| conversion example]].
* MeeGo build tools and Infrastructure derive from Moblin.
* MeeGo uses [[Build_System| OpenSUSE Build Services (OBS)]]; see [[Build Infrastructure]] for details.

== Packaging Guidelines ==

Evolving [[Packaging/Guidelines|packaging guidelines]]...

== Upstream ==

MeeGo is an independent distribution : the only upstream is the projects included into MeeGo such as: kernel.org, X.org, Qt, etc. MeeGo policy is to push all bug fixes to upstream projects.

Why not be <your-favourite-distro>-based? Having an upstream distribution has advantages and disadvantages:
* Advantages: you benefit from all the packaging, QA and maintenance done in the upstream distribution, thus there is a large selection of available ported software.
* Disadvantages: you have to align your build infrastructure with your upstream. You are dependent on the release cycle and architecture choices of upstream.

MeeGo is tailored for its target devices, which are quite specific.

MeeGo will be Linux Standard Base (LSB) compliant.

[[Category:Packaging]]

Build Infrastructure/Packagers Developers/CLI Part 2

2011-04-18T14:58:50Z

Uhofemeier:

= How to use the MeeGo / OBS Command Line Interface, Part 2 =

You've used the set up the 'osc' tool in [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|Part 1]] and now it's time to check out your project for local editing and build.

== Find the project to checkout ==

You can list projects you can check out using 'osc ls'. You will see your home project you created in the Web UI listed too:

$ osc ls
MeeGo
MeeGo:Base:build
MeeGo:Devel
MeeGo:Trunk
MeeGo:Trunk:Extra
MeeGo:Trunk:Extra:rebuild
...
home:<login>
...

== Change to your OBS area ==

Create a directory for doing work and change directory into it:

$ mkdir ~/obs
$ cd ~/obs

== Check out the desired project ==

This is a lot like using Subversion or CVS as the model is 'checkout' and 'checkin' (abbreviated 'co' and 'ci', respectively):

$ osc co home:<login>
A home:<login>
A home:<login>:bash
A home:<login>:bash/Makefile
...

You will now find your checked out project ready for modification and rebuild under home:<login>/<packagename>

== Branching a package to your home project ==

If using MeeGo OBS:

$ osc branch MeeGo.com:Trunk:Testing <packagename> home:<login>:<whatever>

== Summary and next steps ==

This guide gave an introduction on how to use the osc tool to checkout sources.
The next page will cover building your project. Click [[Build_Infrastructure/Packagers_Developers/CLI_Part_3|TBD]] to open the 3rd part.

[[Category:Build Infrastructure]]

Build Infrastructure/Packagers Developers

2011-04-15T17:48:32Z

Uhofemeier:

These pages are in preparation - contributions welcome.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.
Note: You need an account to access build.meego.com.
If you have no account, you can still learn how the openSUSE Build Service works at the upstream project's own instance [http://build.opensuse.org http://build.opensuse.org] .

In this track, you'll learn how to use the webinterface, the commandline client and create your first package.
The packaging guidelines and more advanced topics are also covered.

== How to get started ==

You need an account on build.meego.com:

You will need a meego.com account. To request an account:
# Go to [http://bugs.meego.com MeeGo bugzilla].
# Click New in the upper navigational bar to begin filing a bug.
# On the next page, click MeeGo Community Infrastructure.
# On the following page, click Build Service and file your bug.

== How to use the webinterface ==
A series of pages will make you familiar with webinterface basics. It's divided into several subpages:
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
* [http://wiki.meego.com/Developing_in_a_MeeGo_Environment#Building_your_package|Step_by_step Part 3 - Your first own package]

== OBS - User Home ==
* [[OBS_-_User_Home|How to use]]

== How to use the commandline client ==
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout of projects, commit]]
* Part 3 - branch, edit, localbuild, commit, submitreq
* part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

== MeeGo Packaging guidelines and Howto ==
* [[Packaging|Packaging]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Packaging Tutorial]]

== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
See the [[Quality]] page.

== Verifying Your Package Changes Locally and Online ==
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]

== IRC / mailinglists / contact ==

If you need help, you can join #meego or #meego-dev on irc.freenode.net . See also [[Community communication|this page]] about all MeeGo IRC channels.

You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].

[[Category:Build Infrastructure]]

Build Infrastructure/Packagers Developers

2011-04-15T17:44:45Z

Uhofemeier: /* How to use the webinterface */

These pages are in preparation - contributions welcome.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.
Note: You need an account to access build.meego.com.
If you have no account, you can still learn how the openSUSE Build Service works at the upstream project's own instance [http://build.opensuse.org http://build.opensuse.org] .

In this track, you'll learn how to use the webinterface, the commandline client and create your first package.
The packaging guidelines and more advanced topics are also covered.

== How to get started ==

You need an account on build.meego.com:

You will need a meego.com account. To request an account:
# Go to [http://bugs.meego.com MeeGo bugzilla].
# Click New in the upper navigational bar to begin filing a bug.
# On the next page, click MeeGo Community Infrastructure.
# On the following page, click Build Service and file your bug.

== How to use the webinterface ==
A series of pages will make you familiar with webinterface basics. It's divided into several subpages:
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
*http://wiki.meego.com/Developing_in_a_MeeGo_Environment#Building_your_package:_Step_by_step Part 3 - Your first own package

== OBS - User Home ==
* [[OBS_-_User_Home|How to use]]

== How to use the commandline client ==
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout of projects, commit]]
* Part 3 - branch, edit, localbuild, commit, submitreq
* part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

== MeeGo Packaging guidelines and Howto ==
* [[Packaging|Packaging]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Packaging Tutorial]]

== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
See the [[Quality]] page.

== Verifying Your Package Changes Locally and Online ==
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]

== IRC / mailinglists / contact ==

If you need help, you can join #meego or #meego-dev on irc.freenode.net . See also [[Community communication|this page]] about all MeeGo IRC channels.

You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].

[[Category:Build Infrastructure]]

Build Infrastructure/Packagers Developers/WebUI part 2

2011-04-15T17:39:10Z

Uhofemeier:

= Creating a link and adding a repository =

Welcome to the MeeGo OBS webinterface guide - part 2. We'll show you how you can log in and use the web interface hosted at build.meego.com. This includes login, adding a link to a package in your personal workspace (home:) and how to build that package by adding a repository.

== Start page and Login ==

Open your favorite browser and navigate to https://build.meego.com. You'll be directed to the start page.

[[File:Build_meego_startpage.png|center|alt=build.meego.com|build.meego.com start page.]]

To proceed, you'll need to log in and authenticate with your username and your password.
Enter the data in the upper right corner.

[[File:Build_meego_startpage_arrow.png|center|alt=build.meego.com|build.meego.com log in.]]

After successful authentication, you'll end up on the start page again - with new options visible.

[[File:Build_meego_startpage_loggedin.png|center|alt=build.meego.com|build.meego.com log in.]]

== Create a link to a package in your home: ==

Enter "My Projects" by clicking on the link at the bottom left. You'll see this page as setup in part 1:

[[File:Build_meego_my_projects.png|center]]

Now let's create a link to a package and add a repository to build against. A link is basically a pointer to sources of an already existing package in another project. By *repository*, we mean a build target - like Trunk/Fedora_12/openSUSE_11.2. Let's follow these steps:
# Add link to the existing package.
# Add repository / build target.
# Enable the build (optional, if not already enabled).
# Observe the build on the monitor page
# Look at package's page

=== Add link to existing package ===
Right below packages, there's "Link Package from other Project" .

[[File:Build_meego_empty_home_arrow.png|center]]

Open that page and enter for
Name of original project:
MeeGo:1.0:Core
and for
Name of package in original project:
bash
- we'll leave "Name of linked package in target project" empty.

This is shown on the next picture:

[[File:Build_meego_addlink1.png|center]]

Proceed with "Create Link" and you'll be redirected to your home again. You'll see a new package "bash" and a notice about the link being added.

[[File:Build_meego_link_added_arrows.png|center]]

Wonderful, we've added a pointer to the sources - now we need a build repository added, so the builder knows the target-distribution.

=== Add repository / build target ===
To do this, click on "Add Repository". This will look like:

[[File:Build_meego_add_repo.png|center]]

Now select "Meego:Trunk/standard" as target repository:

[[File:Build_meego_add_repo_2.png|center]]

(If it is not in the initial list, see if there an an Advanced link to a more comprehensive list). This will take you back to your home: project. The build repository might be disabled: if so, klick on the cogwheel to enable it.

[[File:Build_meego_trunk_added_arrows.png|center]]

Congratulations, it is configured. On a heavily loaded server, it can sometimes take a few minutes for your changes to become effective, but your linked package will automatically begin building.

=== Package page, build log and project monitor page ===
Next, it is time to explore the Monitor page, the package detail page and the build log. Just click on the links and explore the web interface.

I recommend starting with your home project's top level 'overview' page - click on the Overview tab and you may see something like this:

[[File:Build_meego_home_project_failed_build.png|center]]

This page has shown that some builds for some packages failed to complete successfully. Let's go look at the package itself. Click on the 'Packages' tab and then on 'bash'. You'll see the package detail page:

[[File:Build_meego_package_overview.png|center]]

What failed? You can click on ''failed'' for either of the packages builds to inspect the build log. Below are the top of that page:

[[File:Build_meego_building_log.png|center]]
... and the bottom of the build log page:
[[File:Build_meego_building_log2.png|center]]

The comment at the end hints that the package probably built OK and rpms were produced, but that there were style violations in the packaging tests mandated by the MeeGo project. In fact, all that is confirmed some lines above when the rpmlint test is started:

[[File:Build_meego_building_log_err.png|center]]

Return using your browser back button to your home project Overview page. Click on the Monitor tab, and you'll see something like:

[[File:Build_meego_building_monitor.png|center]]

So you can monitor something as it is building, let's add the ''acl'' package too. Click on the ''Packages'' tab. Then, click ''Link package'' from another project. Enter ''MeeGo:1.0:Core'' as the original project and ''acl'' as the name of package, and click ''Create Link''. Return to your home project. Click on the Monitor tab and it will look like:

[[File:Build_meego_building_monitor_2.png|center]]

Feel free to inspect the logs as each version of the package is building.

== Repository Output: Built Packages ==

To find the RPMs you built, go to your home project page and click Repositories. From there click on the repository name. For example, ''Trunk'':

[[File:Build_meego_built_repos_arrow.png]]

And from there, click on ''Go to download repository''. You'll see something like this:

[[File:Build_meego_built_repos_download.png]]

Your rpms can be found in the subdirectories, and the .repo file is suitable for use with zypper, yum or other repository-friendly package management tools.

== Summary ==

We've had a look at adding a linked package. We watched it build automatically, pulling in prerequisite source packages, and inspected the logs. We also located the final output: built package files: source and binary rpm files. In our next step, we'll show how you can set up your own first package using the web interface -- continue at [[Build_Infrastructure/Packagers_Developers/WebUI_part_3|Part 3]].

Build Infrastructure/Packagers Developers/WebUI part 1

2011-04-15T17:38:08Z

Uhofemeier:

= How to use the MeeGo / OBS Web Interface =

Welcome to the MeeGo / OBS Web Interface guide. We'll show you how you can log in and use the interface being hosted at build.meego.com. This includes login, creation of the personal home: project, monitoring and creating a simple package using the interface.

== Register for an OBS account ==
http://bugs.meego.com

== Start page and Login ==

Open your favorite browser and navigate to https://build.meego.com (MeeGo)

[[File:Build_meego_startpage.png|center|alt=build.meego.com|build.meego.com startpage.]]

To proceed, you'll need to log in and authenticate with your username and your password.
Click on Login and enter the data in the upper right corner.

[[File:Build_meego_startpage_arrow.png|center|alt=build.meego.com|build.meego.com login.]]

After successful authentication, you'll end up on the start page again - with new options visible.
We'll go through most of them in detail, but first lets create your home: in the next step.

[[File:Build_meego_startpage_loggedin.png|center|alt=build.meego.com|build.meego.com login.]]

== Create your home: project ==

Every developer has his/her home:<userid> project where he/she has write access by default. This is like your personal
project or dashboard where you can experiment and play. But first you need to enter some lines to describe your home project. Click on the link "Home Project" at the bottom left and answer the questions.

[[File:Build_meego_startpage_loggedin_arrow_home.png|center|alt=build.meego.com|build.meego.com log in.]]

Now you are redirected to your home: . It will be empty for now, but as you see in the picture below, you can add ''packages'' containing the sources/build recipes and ''projects'' which are the containers for the build targets. As you can see, you're the default maintainer which grants you full write access to this project. You're also the bug owner of your project.

[[File:Build_meego_home_project.png|center]]

== My Projects, Server Status ==
Let's leave for now your home: for a bit and explore the build service. Click on "My Projects" on the left at the bottom. This opens a page listing your watched projects and your involvements in projects or packages.

[[File:Build_meego_my_projects.png|center]]

Now, let's visit the main monitor page by clicking on "Server Status". You see here the status of the services, some graphs and graphics showing the currently running and completed jobs an the overall load.

[[File:Build_meego_monitor_page.png|center]]

== Summary and next steps ==

This guide gave an introduction on how to log in and se tup your home: and how to reach "My Projects" and the "Server Status" pages.
Now it's time to create your own package and build it. Click [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|here]] to open the 2nd part.

[[Category:Build Infrastructure]]

Release Engineering/Process

2011-04-14T22:09:39Z

Uhofemeier:

== The iterative development model - weekly cycles ==

Between releases in the active development cycle, work for MeeGo will run in weekly iterations, producing nightly builds and weekly releases from the Trunk. The resulting build from each iteration is used to track development progress. The diagram below shows the timing for the weekly cycle - unless otherwise noted in the diagram, all times are GMT.

== Development Builds ==

Daily is the repository where the trunk output with the latest changes lands. This is the bleeding edge of development. This repository can be added to images but should be disabled by default. <br>

== Iteration cycle schedule ==

MeeGo images created and delivered to [[Quality|QA]] and are non-official images. They serve to test major changes introduced into the Trunk testing. Release Engineers have the discretion to accept, reject, or queue submitted changes after the image has been finalized. Feedback may be given to make sure the usability of the upcoming weekly releases for the users of MeeGo.<br>
In principle, changes can still go in for the final weekly release, if the changes meet the following criteria:
* The change is not a major API change
* The change is not a base system or tool-chain change
* The change addresses a showstopper found by [[Quality|QA]] in the image release
* ...

<p>[[File:WeeklyReleaseCycle.png|frame|left|'''Timing for Weekly Iteration Cycle (all times GMT unless otherwise noted)''']]</p>
<br style="clear: both" />

== How the code reaches the Trunk/Release ==

Integrating new code to Trunk or a release must not break the MeeGo reference images. The reference images represent product categories, SDK, and other configurations that need to be in place for MeeGo to function, development to continue, and products to use MeeGo. MeeGo will provide facilities to help developers test against the different references. <br>
The first level of integration is called Staging, where developers work with the packages in OBS development projects. The package maintainer pushes the project towards the MeeGo :Testing projects. MeeGo will provide an automated testing facility where test cases can be contributed. This will provide results from the different MeeGo references, since in many cases it is not feasible to obtain all the different reference devices. <br>
When test results are of a sufficient standard, the package maintainer pushes his/her code towards the MeeGo :Testing project. These contributions are reviewed by the MeeGo Distribution/Platform maintainers and tested against the current Trunk. If they pass, QA packages are promoted to the Trunk.

<p>[[File:MeeGoIntegrationFlow.JPG]]</p>

=== Package quality expectation in devel:* projects ===

* Package is following [[Packaging/Guidelines|packaging guidelines]]
* Package is compilable against [[Release_Engineering/Repo_List|target project]]
* Package is tested on relevant hardware platform
* '''If package introducing intrusive changes, maintainer should inform Release Engineering team by sending mail to meego-releases@meego.com mailing list
'''

=== Package quality expectations for submissions into *:Testing projects ===

==== Step 1: Review by Release Engineers ====

* Package follows [[Packaging/Guidelines|packaging guidelines]]
* A new package must have a Feature in bugzilla corresponding to it.
** If none exist, file a feature request through bugzilla with a description of why this package is needed in MeeGo.
** This feature request must then be approved in the product management forum and set to state ACCEPTED.
* Package upgrades must have a Feature or Bug # corresponding to it.
** If none exists, file new Bug or Feature and describe why this change is needed in MeeGo
** For minor upgrades to pkgs that mostly include bug fixes, a Bug will suffice. For major upgrades that include new features or major API changes, a Feature # is required.
** '''Note:''' If your package upgrade doesn't touch code, and is merely a cosmetic (configuration) change, no Bug number is required.
* Package is submitted from corresponding devel:* project by one of project maintainers.
* Package has clear change description and references to bugs and/or features (see [[Packaging/Guidelines#External_References|packaging guidelines on format]])
* Bug or Feature referenced must have proper values in following fields:
** Status = RESOLVED
** Version = MeeGo release to which item is targeting
** Target Build = MeeGo weekly build to which item is targeting

==== Step 2: Compilation and Images ====

* Packages should compile correctly in *:Testing repositories for all target architectures
* Packages should not break compilation of other dependant packages
* Packages should not break creation of all needed reference images

Note: Processing of requests containing packages that delve lower in the dependency hierarchy may be postponed (usually done during the weekends). This is due to the fact that processing the said package(s) will trigger a lot of rebuilds and the builders are comparatively idle during the weekends. [[Release_Engineering/lower_level_pkgs|Here]] is a sample list of 'special' packages.

==== Step 3: Developer Submission Check-list ====

* Here is a helpful check-list that developer's can go through before a submission. It covers all of the the above in an easy-to-follow manner. It also includes an FAQ and top common problems that developers go through when submitting that ends up in a rejection of the request.

[[Release_Engineering/Submission_Checklist|Developer Submission Checklist]]

=== Acceptance criteria for Trunk ===

* Release Engineers are responsible for smoke-testing medium and big changes on relevant hardware.
* Based on QA test results, accumulated changes to be promoted to Trunk (or Release) if those changes are not causing any regressions compared to Trunk (or Release)

=== Release acceptance criteria ===

* All required images should be built and smoke-tested by responsible release
* All required images should have no regressions, based on QA reports
** If build has no regressions, release is made
** If build contains regressions, based on QA reports Release Manager makes a decision
*** release with documented limitations
*** introduce some changes and re-iterate release procedure

== Making a product out of MeeGo Release ==

MeeGo supports a wide range of different categories of products and the release process tries to accommodate the different requirements of each product category. The Release process takes into account the following three aspects of successful product creation:
# Fast time-to-market by supporting QA in contributed reference HW for all contributions
# Fast development cycles by providing facilities to do upstream development within MeeGo and enabling easy synchronization to weekly releases via the release preview practice
# Fully open toolset for any HW or SW vendor to use for efficient SW creation

<p>[[File:MeeGoReleaseCollaboration.JPG]]</p>

[[Category:Release engineering]]

Release Engineering/Process

2011-04-14T22:08:44Z

Uhofemeier:

== The iterative development model - weekly cycles ==

Between releases in the active development cycle, work for MeeGo will run in weekly iterations, producing nightly builds and weekly releases from the Trunk. The resulting build from each iteration is used to track development progress. The diagram below shows the timing for the weekly cycle - unless otherwise noted in the diagram, all times are GMT.

== Development Builds ==

Daily is the repository where the trunk output with the latest changes lands. This is the bleeding edge of development. This repository can be added to images but should be disabled by default. <br>

== Iteration cycle schedule ==

MeeGo images created and delivered to [[Quality|QA]] and are non-official images. They serve to test major changes introduced into the Trunk testing. Release Engineers have the discretion to accept, reject, or queue submitted changes after the image has been finalized. Feedback may be given to make sure the usability of the upcoming weekly releases for the users of MeeGo.<br>
In principle, changes can still go in for the final weekly release, if the changes meet the following criteria:
* The change is not a major API change
* The change is not a base system or tool-chain change
* The change addresses a showstopper found by [[Quality|QA]] in the image release
* ...

<p>[[File:WeeklyReleaseCycle.png|frame|left|'''Timing for Weekly Iteration Cycle (all times GMT unless otherwise noted)''']]</p>
<br style="clear: both" />

== How the code reaches the Trunk/Release ==

Integrating new code to Trunk or a release must not break the MeeGo reference images. The reference images represent product categories, SDK, and other configurations that need to be in place for MeeGo to function, development to continue, and products to use MeeGo. MeeGo will provide facilities to help developers test against the different references. <br>
The first level of integration is called Staging, where developers work with the packages in OBS development projects. The package maintainer pushes the project towards the MeeGo :Testing projects. MeeGo will provide an automated testing facility where test cases can be contributed. This will provide results from the different MeeGo references, since in many cases it is not feasible to obtain all the different reference devices. <br>
When test results are of a sufficient standard, the package maintainer pushes his/her code towards the MeeGo :Testing project. These contributions are reviewed by the MeeGo Distribution/Platform maintainers and tested against the current Trunk. If they pass, QA packages are promoted to the Trunk.

<p>[[File:MeeGoIntegrationFlow.JPG]]</p>

=== Package quality expectation in devel:* projects ===

* Package is following [[Packaging/Guidelines|packaging guidelines]]
* Package is compilable against [[Release_Engineering/Repo_List|target project]]
* Package is tested on relevant hardware platform
* '''If package introducing intrusive changes, maintainer should inform Release Engineering team by sending mail to meego-releases@meego.com mailing list
'''

=== Package quality expectations for submissions into *:Testing projects ===

==== Step 1: Review by Release Engineers ====

* Package follows [[Packaging/Guidelines|packaging guidelines]]
* A new package must have a Feature in bugzilla corresponding to it.
** If none exist, file a feature request through bugzilla with a description of why this package is needed in MeeGo.
** This feature request must then be approved in the product management forum and set to state ACCEPTED.
* Package upgrades must have a Feature or Bug # corresponding to it.
** If none exists, file new Bug or Feature and describe why this change is needed in MeeGo
** For minor upgrades to pkgs that mostly include bug fixes, a Bug will suffice. For major upgrades that include new features or major API changes, a Feature # is required.
** '''Note:''' In case your package upgrade doesn't touch code, but is a cosmetic (configuration) change, a Bug number is not required.
* Package is submitted from corresponding devel:* project by one of project maintainers.
* Package has clear change description and references to bugs and/or features (see [[Packaging/Guidelines#External_References|packaging guidelines on format]])
* Bug or Feature referenced must have proper values in following fields:
** Status = RESOLVED
** Version = MeeGo release to which item is targeting
** Target Build = MeeGo weekly build to which item is targeting

==== Step 2: Compilation and Images ====

* Packages should compile correctly in *:Testing repositories for all target architectures
* Packages should not break compilation of other dependant packages
* Packages should not break creation of all needed reference images

Note: Processing of requests containing packages that delve lower in the dependency hierarchy may be postponed (usually done during the weekends). This is due to the fact that processing the said package(s) will trigger a lot of rebuilds and the builders are comparatively idle during the weekends. [[Release_Engineering/lower_level_pkgs|Here]] is a sample list of 'special' packages.

==== Step 3: Developer Submission Check-list ====

* Here is a helpful check-list that developer's can go through before a submission. It covers all of the the above in an easy-to-follow manner. It also includes an FAQ and top common problems that developers go through when submitting that ends up in a rejection of the request.

[[Release_Engineering/Submission_Checklist|Developer Submission Checklist]]

=== Acceptance criteria for Trunk ===

* Release Engineers are responsible for smoke-testing medium and big changes on relevant hardware.
* Based on QA test results, accumulated changes to be promoted to Trunk (or Release) if those changes are not causing any regressions compared to Trunk (or Release)

=== Release acceptance criteria ===

* All required images should be built and smoke-tested by responsible release
* All required images should have no regressions, based on QA reports
** If build has no regressions, release is made
** If build contains regressions, based on QA reports Release Manager makes a decision
*** release with documented limitations
*** introduce some changes and re-iterate release procedure

== Making a product out of MeeGo Release ==

MeeGo supports a wide range of different categories of products and the release process tries to accommodate the different requirements of each product category. The Release process takes into account the following three aspects of successful product creation:
# Fast time-to-market by supporting QA in contributed reference HW for all contributions
# Fast development cycles by providing facilities to do upstream development within MeeGo and enabling easy synchronization to weekly releases via the release preview practice
# Fully open toolset for any HW or SW vendor to use for efficient SW creation

<p>[[File:MeeGoReleaseCollaboration.JPG]]</p>

[[Category:Release engineering]]

Release Engineering/Process

2011-04-14T22:02:29Z

Uhofemeier:

== The iterative development model - weekly cycles ==

Between releases in the active development cycle, work for MeeGo will run in weekly iterations, producing nightly builds and weekly releases from the Trunk. The resulting build from each iteration is used to track development progress. The diagram below shows the timing for the weekly cycle - unless otherwise noted in the diagram, all times are GMT.

== Development Builds ==

Daily is the repository where the trunk output with the latest changes lands. This is the bleeding edge of development. This repository can be added to images but should be disabled by default. <br>

== Iteration cycle schedule ==

MeeGo images created and delivered to [[Quality|QA]] and are non-official images. They serve to test major changes introduced into the Trunk testing. Release Engineers have the discretion to accept, reject, or queue submitted changes after the image has been finalized. Feedback may be given to make sure the usability of the upcoming weekly releases for the users of MeeGo.<br>
In principle, changes can still go in for the final weekly release, if the changes meet the following criteria:
* The change is not a major API change
* The change is not a base system or tool-chain change
* The change addresses a showstopper found by [[Quality|QA]] in the image release
* ...

<p>[[File:WeeklyReleaseCycle.png|frame|left|'''Timing for Weekly Iteration Cycle (all times GMT unless otherwise noted)''']]</p>
<br style="clear: both" />

== How the code reaches the Trunk/Release ==

Integrating new code to Trunk or a release must not break the MeeGo reference images. The reference images represent product categories, SDK, and other configurations that need to be in place for MeeGo to function, development to continue, and products to use MeeGo. MeeGo will provide facilities to help developers test against the different references. <br>
The first level of integration is called Staging, where developers work with the packages in OBS development projects. The package maintainer pushes the project towards the MeeGo :Testing projects. MeeGo will provide an automated testing facility where test cases can be contributed. This will provide results from the different MeeGo references, since in many cases it is not feasible to obtain all the different reference devices. <br>
When test results are of a sufficient standard, the package maintainer pushes his/her code towards the MeeGo :Testing project. These contributions are reviewed by the MeeGo Distribution/Platform maintainers and tested against the current Trunk. If they pass, QA packages are promoted to the Trunk.

<p>[[File:MeeGoIntegrationFlow.JPG]]</p>

=== Package quality expectation in devel:* projects ===

* Package is following [[Packaging/Guidelines|packaging guidelines]]
* Package is compilable against [[Release_Engineering/Repo_List|target project]]
* Package is tested on relevant hardware platform
* '''If package introducing intrusive changes, maintainer should inform Release Engineering team by sending mail to meego-releases@meego.com mailing list
'''

=== Package quality expectations for submissions into *:Testing projects ===

==== Step 1: Review by Release Engineers ====

* Package follows [[Packaging/Guidelines|packaging guidelines]]
* A new package must have a Feature in bugzilla corresponding to it.
** If none exist, file a feature request through bugzilla with a description of why this package is needed in MeeGo.
** This feature request must then be approved in the product management forum and set to state ACCEPTED.
* Package upgrades must have a Feature or Bug # corresponding to it.
** If none exists, file new Bug or Feature and describe why this change is needed in MeeGo
** For minor upgrades to pkgs that mostly include bug fixes, a Bug will suffice. For major upgrades that include new features or major API changes, a Feature # is required.
* Package is submitted from corresponding devel:* project by one of project maintainers.
* Package has clear change description and references to bugs and/or features (see [[Packaging/Guidelines#External_References|packaging guidelines on format]])
* Bug or Feature referenced must have proper values in following fields:
** Status = RESOLVED
** Version = MeeGo release to which item is targeting
** Target Build = MeeGo weekly build to which item is targeting

==== Step 2: Compilation and Images ====

* Packages should compile correctly in *:Testing repositories for all target architectures
* Packages should not break compilation of other dependant packages
* Packages should not break creation of all needed reference images

Note: Processing of requests containing packages that delve lower in the dependency hierarchy may be postponed (usually done during the weekends). This is due to the fact that processing the said package(s) will trigger a lot of rebuilds and the builders are comparatively idle during the weekends. [[Release_Engineering/lower_level_pkgs|Here]] is a sample list of 'special' packages.

==== Step 3: Developer Submission Check-list ====

* Here is a helpful check-list that developer's can go through before a submission. It covers all of the the above in an easy-to-follow manner. It also includes an FAQ and top common problems that developers go through when submitting that ends up in a rejection of the request.

[[Release_Engineering/Submission_Checklist|Developer Submission Checklist]]

=== Acceptance criteria for Trunk ===

* Release Engineers are responsible for smoke-testing medium and big changes on relevant hardware.
* Based on QA test results, accumulated changes to be promoted to Trunk (or Release) if those changes are not causing any regressions compared to Trunk (or Release)

=== Release acceptance criteria ===

* All required images should be built and smoke-tested by responsible release
* All required images should have no regressions, based on QA reports
** If build has no regressions, release is made
** If build contains regressions, based on QA reports Release Manager makes a decision
*** release with documented limitations
*** introduce some changes and re-iterate release procedure

== Making a product out of MeeGo Release ==

MeeGo supports a wide range of different categories of products and the release process tries to accommodate the different requirements of each product category. The Release process takes into account the following three aspects of successful product creation:
# Fast time-to-market by supporting QA in contributed reference HW for all contributions
# Fast development cycles by providing facilities to do upstream development within MeeGo and enabling easy synchronization to weekly releases via the release preview practice
# Fully open toolset for any HW or SW vendor to use for efficient SW creation

<p>[[File:MeeGoReleaseCollaboration.JPG]]</p>

[[Category:Release engineering]]

Build Infrastructure/Sysadmin Distro/OBS setup openSUSE114

2011-01-13T19:07:51Z

Uhofemeier:

Please check http://gitorious.org/opensuse/build-service/blobs/master/dist/README.SETUP
for the latest setup instructions!
<p>
These steps are to setup Open Build Service 1.7.5 on an openSuSE 11.2 installation. Currently this document describes how to setup an evaluation/test setup and is not meant as a production setup.
</p>
<p>
Most users won't need to install their own OBS and can just use an account on a publicly accessible OBS. Once public access is allowed to the global MeeGo OBS, there will be a link to obtain access.
</p>
<p>
There are cases where vendors may rather have full control of their builds and keep source private due to licensing restrictions, etc. These instructions are for these special cases.
</p>
<p>
MeeGo will switch to version 2.1 of the Build Service which is to be released soon. These instructions will be updated for the new version as soon as possible.
</p>

<h2>Add Repositories</h2>

First, we have to add the openSUSE:Tools repository to zypper for qemu-svn and other updated tools.

<code>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
</code>

Accept the trust key.

<h2>Setup the Client</h2>
<h3>Install the Client Packages</h3>

*For obs worker:
<code>
zypper in obs-worker qemu-svn mount-static bash-static
</code>

<h3>Point To The Server</h3>
<p>
Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server. (The example server is 192.168.1.1)
</p>
<code>
# vi /etc/sysconfig/obs-worker
OBS_SRC_SERVER="192.168.1.1:5352"
OBS_REPO_SERVERS="192.168.1.1:5252"
</code>

<h3>Start the Client</h3>
<p>Start the worker service
</p>
<code>
chkconfig --add obsworker
rcobsworker start
</code>

<h2>Setup the server</h2>

<h3>Install the Server packages</h3>

*For server:
<code>
zypper in obs-server obs-signer obs-utils createrepo nfs-client obs-api memcached lighttpd
</code>

<h3>MySQL Setup</h3>
Start daemon by default:
<code>
chkconfig --add mysql
rcmysql start
</code>

Secure the installation
<code>
/usr/bin/mysql_secure_installation
</code>

Create the databases:
<code>
mysql -u root -p
mysql> create database api_production;
mysql> create database webui_production;
</code>

Add the obs user for these databases (substitute the correct password in):

<code>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</code>

Now, configure OBS to use MySQL, first the API server.

<code>
vi /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</code>
And setup the webui to use MySQL...
<code>
vi /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</code>

Populate the database
<code>
cd /srv/www/obs/api/
RAILS_ENV="production"
rake db:setup

cd /srv/www/obs/webui/
RAILS_ENV="production"
rake db:setup
</code>
If this fails, check /srv/www/obs/api/config/environments/production.rb and /srv/www/obs/webui/config/environments/production.rb for configuration of the SOURCE_HOST and FRONTEND_HOST.

<h3>Setup lighttpd for webui</h3>
Make sure vhosts are enabled by uncommenting the following line:
<code>
# vi /etc/lighttpd/lighttpd.conf
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</code>
Setup the regular webui on 80, api on 81, and 82 is the repository.
<code>
vi /etc/lighttpd/vhosts.d/obs.conf
$SERVER["socket"] == ":80" {
rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/webui/log"
include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":81" {
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":82" {
server.name = "192.168.1.1"
server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}

</code>
<p>
lighttpd requires some extra modules to be enabled: mod_access, mod_rewrite, mod_magnet, and mod_fastcgi. Do so by editing /etc/lighttpd/modules.conf:
</p>
<code>
# vi /etc/lighttpd/modules.conf
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</code>

<p>
You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:
</p>
<code>
# vi /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "192.168.1.1"
FRONTEND_PORT = 81
FRONTEND_PROTOCOL = 'http'
BUGZILLA_HOST = nil
DOWNLOAD_URL = "http://192.168.1.1:82"
ICHAIN_MODE = "off"
BASE_NAMESPACE = nil
</code>

<p>
Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:
</p>
<code>
# vi /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "192.168.1.1"
</code>

<p>
Add the server to start by default.
</p>
<code>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed
</code>

<p>
ligthttpd user and group need to be the onwer of api and webui dirs (as well as log and tmp):
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>

<h3>BSConfig.pm</h3>
<p>
The file <i>/usr/lib/obs/server/BSConfig.pm</i> is used to configure several settings for the Build Service. One of the major components is setting up the $hostname variable to the correct value. Currently I have this set to the IP address of the server.
</p>

<code>
my $hostname = '192.168.1.1';
</code>

<p>
The list of directories in /srv/obs/repos/ is the repositories, so I changed the $repodownload:
</p>

<code>
our $repodownload = "http://$hostname:82/";
</code>

<h3>Verification</h3>
<p>
At this point you should be able to open a browser and go to your server and login to OBS. Port 80 should be the webui, port 81 should be the api, and port 82 should be the repository directory. The default username/password is Admin/opensuse.
</p>
<h3>Start By Default</h3>

<p>The OBS should start automatically, so they should be added to chkconfig to do so:</p>
<code>
chkconfig --add obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher obswarden obssigner
</code>

<h2>Setting up Cross Compile</h2>
<h3>Configure build types</h3>
<p>
To setup cross compile, add the appropriate machine types to /etc/sysconfig/obs-server. For example, the following will enable ARM builds.
</p>
<code>
# vi /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 armv5el armv7el“
</code>

<h2>Cloning Repositories</h2>

<h3>prj and prjconf</h3>
<p>The project settings and the project config is an important part of the project and should be copied to the local project setup.</p>
<code>
osc -A <remote API URL> meta prj <repository name> > prj.txt
osc -A <remote API URL> meta prjconf <repository name> > prjconf.txt
</code>
<p>
Modify the prj.txt file to name valid users in the userid fields. Once modified, the settings and configuration can be applied to the local project.
</p>
<code>
osc -A <local API URL> meta prj <repository name> -F prj.txt
osc -A <local API URL> meta prjconf <repository name> -F prjconf.txt
</code>

<h3>Mirror</h3>
<p>
obs_mirror_project (/usr/sbin/obs_mirror_project) is used to copy an external OBS project. The script needed to be modified to use build.meego.com as apposed to the hard coded download.opensuse.org site. You need an login to build.meego.com to execute this script.
</p>
<code>
/usr/sbin/obs_mirror_project <repository name> <type> <arch>
</code>

<h3>Rescan Repository</h3>
<p>Once the download of the project is complete, you have to rescan the local repository.</p>
<code>
/usr/lib/obs/server/bs_admin --rescan-repository <repository name> <type> <arch>
</code>

<h2>Troubleshooting</h2>
<p>
Here are common issues that have been seen and how to resolve them.
</p>

<h3>HTTP Error 500</h3>
<p>
Check <b>/srv/www/obs/api/config/environments/production.rb</b>
and <b>/srv/www/obs/webui/config/environments/production.rb</b> for configuration of the
<b>SOURCE_HOST</b> and <b>FRONTEND_HOST</b>.
</p>
<h3>Cannot load person data for Admin in application_helper</h3>
<p>
Make sure you set the permissions on the api and webui directories.
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>
<p>
If this doesn't work then try to recreate the databases:
</p>
<code>
# mysql -u root -p
mysql> drop database api_production;
mysql> drop database webui_production;
</code>
<p>
Rerun the mysql database setup from above and re-run rake.
</p>
----
<h2>External Links</h2>
<p>
<ul>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Installation Maemo OBS Installation]
</li>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup Maemo Fremantel Setup]
</li>
</ul>
</p>
----
[[User:Liam | Liam]]

[[User:Dl9pf | Dl9pf]]

[[Category:Build Infrastructure]]

Build Infrastructure/Sysadmin Distro/OBS setup openSUSE114

2011-01-13T19:06:06Z

Uhofemeier:

Please check http://gitorious.org/opensuse/build-service/blobs/master/dist/README.SETUP
for the latest setup instructions!
<p>
These steps are to setup Open Build Service 1.7.5 on an openSuSE 11.2 installation. Currently this document describes how to setup an evaluation/test setup and is not meant as a production setup.
</p>
<p>
Most users won't need to install their own OBS and can just use an account on a publicly accessible OBS. Once public access is allowed to the global MeeGo OBS, there will be a link to obtain access.
</p>
<p>
There are cases where vendors may rather have full control of their builds and keep source private due to licensing restrictions, etc. These instructions are for these special cases.
</p>
<p>
MeeGo will switch to version 2.1 of the Build Service which is to be released soon. These instructions will be updated for the new version as soon as possible.
</p>

<h2>Add Repositories</h2>

First, we have to add the openSUSE:Tools repository to zypper for qemu-svn and other updated tools.

<code>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
</code>

Accept the trust key.

<h2>Setup the Client</h2>
<h3>Install the Client Packages</h3>

*For obs worker:
<code>
zypper in obs-worker qemu-svn mount-static bash-static
</code>

<h3>Point To The Server</h3>
<p>
Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server. (The example server is 192.168.1.1)
</p>
<code>
# vi /etc/sysconfig/obs-worker
OBS_SRC_SERVER="192.168.1.1:5352"
OBS_REPO_SERVERS="192.168.1.1:5252"
</code>

<h3>Start the Client</h3>
<p>Start the worker service
</p>
<code>
chkconfig --add obsworker
rcobsworker start
</code>

<h2>Setup the server</h2>

<h3>Install the Server packages</h3>

*For server:
<code>
zypper in obs-server obs-signer obs-utils createrepo nfs-client obs-api memcached lighttpd
</code>

<h3>MySQL Setup</h3>
Start daemon by default:
<code>
chkconfig --add mysql
rcmysql start
</code>

Secure the installation
<code>
/usr/bin/mysql_secure_installation
</code>

Create the databases:
<code>
mysql -u root -p
mysql> create database api_production;
mysql> create database webui_production;
</code>

Add the obs user for these databases (substitute the correct password in):

<code>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</code>

Now, configure OBS to use MySQL, first the API server.

<code>
vi /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</code>
And setup the webui to use MySQL...
<code>
vi /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</code>

Populate the database
<code>
cd /srv/www/obs/api/
RAILS_ENV="production"
rake db:setup

cd /srv/www/obs/webui/
RAILS_ENV="production"
rake db:migrate
</code>
If this fails, check /srv/www/obs/api/config/environments/production.rb and /srv/www/obs/webui/config/environments/production.rb for configuration of the SOURCE_HOST and FRONTEND_HOST.

<h3>Setup lighttpd for webui</h3>
Make sure vhosts are enabled by uncommenting the following line:
<code>
# vi /etc/lighttpd/lighttpd.conf
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</code>
Setup the regular webui on 80, api on 81, and 82 is the repository.
<code>
vi /etc/lighttpd/vhosts.d/obs.conf
$SERVER["socket"] == ":80" {
rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/webui/log"
include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":81" {
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":82" {
server.name = "192.168.1.1"
server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}

</code>
<p>
lighttpd requires some extra modules to be enabled: mod_access, mod_rewrite, mod_magnet, and mod_fastcgi. Do so by editing /etc/lighttpd/modules.conf:
</p>
<code>
# vi /etc/lighttpd/modules.conf
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</code>

<p>
You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:
</p>
<code>
# vi /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "192.168.1.1"
FRONTEND_PORT = 81
FRONTEND_PROTOCOL = 'http'
BUGZILLA_HOST = nil
DOWNLOAD_URL = "http://192.168.1.1:82"
ICHAIN_MODE = "off"
BASE_NAMESPACE = nil
</code>

<p>
Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:
</p>
<code>
# vi /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "192.168.1.1"
</code>

<p>
Add the server to start by default.
</p>
<code>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed
</code>

<p>
ligthttpd user and group need to be the onwer of api and webui dirs (as well as log and tmp):
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>

<h3>BSConfig.pm</h3>
<p>
The file <i>/usr/lib/obs/server/BSConfig.pm</i> is used to configure several settings for the Build Service. One of the major components is setting up the $hostname variable to the correct value. Currently I have this set to the IP address of the server.
</p>

<code>
my $hostname = '192.168.1.1';
</code>

<p>
The list of directories in /srv/obs/repos/ is the repositories, so I changed the $repodownload:
</p>

<code>
our $repodownload = "http://$hostname:82/";
</code>

<h3>Verification</h3>
<p>
At this point you should be able to open a browser and go to your server and login to OBS. Port 80 should be the webui, port 81 should be the api, and port 82 should be the repository directory. The default username/password is Admin/opensuse.
</p>
<h3>Start By Default</h3>

<p>The OBS should start automatically, so they should be added to chkconfig to do so:</p>
<code>
chkconfig --add obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher obswarden obssigner
</code>

<h2>Setting up Cross Compile</h2>
<h3>Configure build types</h3>
<p>
To setup cross compile, add the appropriate machine types to /etc/sysconfig/obs-server. For example, the following will enable ARM builds.
</p>
<code>
# vi /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 armv5el armv7el“
</code>

<h2>Cloning Repositories</h2>

<h3>prj and prjconf</h3>
<p>The project settings and the project config is an important part of the project and should be copied to the local project setup.</p>
<code>
osc -A <remote API URL> meta prj <repository name> > prj.txt
osc -A <remote API URL> meta prjconf <repository name> > prjconf.txt
</code>
<p>
Modify the prj.txt file to name valid users in the userid fields. Once modified, the settings and configuration can be applied to the local project.
</p>
<code>
osc -A <local API URL> meta prj <repository name> -F prj.txt
osc -A <local API URL> meta prjconf <repository name> -F prjconf.txt
</code>

<h3>Mirror</h3>
<p>
obs_mirror_project (/usr/sbin/obs_mirror_project) is used to copy an external OBS project. The script needed to be modified to use build.meego.com as apposed to the hard coded download.opensuse.org site. You need an login to build.meego.com to execute this script.
</p>
<code>
/usr/sbin/obs_mirror_project <repository name> <type> <arch>
</code>

<h3>Rescan Repository</h3>
<p>Once the download of the project is complete, you have to rescan the local repository.</p>
<code>
/usr/lib/obs/server/bs_admin --rescan-repository <repository name> <type> <arch>
</code>

<h2>Troubleshooting</h2>
<p>
Here are common issues that have been seen and how to resolve them.
</p>

<h3>HTTP Error 500</h3>
<p>
Check <b>/srv/www/obs/api/config/environments/production.rb</b>
and <b>/srv/www/obs/webui/config/environments/production.rb</b> for configuration of the
<b>SOURCE_HOST</b> and <b>FRONTEND_HOST</b>.
</p>
<h3>Cannot load person data for Admin in application_helper</h3>
<p>
Make sure you set the permissions on the api and webui directories.
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>
<p>
If this doesn't work then try to recreate the databases:
</p>
<code>
# mysql -u root -p
mysql> drop database api_production;
mysql> drop database webui_production;
</code>
<p>
Rerun the mysql database setup from above and re-run rake.
</p>
----
<h2>External Links</h2>
<p>
<ul>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Installation Maemo OBS Installation]
</li>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup Maemo Fremantel Setup]
</li>
</ul>
</p>
----
[[User:Liam | Liam]]

[[User:Dl9pf | Dl9pf]]

[[Category:Build Infrastructure]]

User:Rolla/image-creation-notes

2010-12-27T18:24:28Z

Uhofemeier:

'''!!! FIRST CHECK IF ALL REPOS HAVE FINISHED BUILDING AND NOTHING FAILS TOO BADLY !!!'''

ssh download.meego.com

sudo su repos

cd

----

*AS USER repos

*If Tuesday
pushd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al builds/trunk/daily builds/trunk/{BUILDID}
popd
cd ./bin
sh diff-trunk-repos {_LAST_BUILDID} {BUILDID}
*check changelog to insure correct repos were are being used to diff
~repos/bin/sync-repos

*Check repo.meego.com/MeeGo/ for expected change

*If Trunk-Daily
pushd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al builds/trunk/daily /srv/www/vhosts/trunk-daily/builds/trunk/{BUILDID}
*copy sdk repo
cd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al sdk/target/repos/meego/trunk /srv/www/vhosts/trunk-daily/builds/trunk/{BUILDID}/sdk
popd
cd ./bin
sh ./diff-trunk-daily-repos {_LAST_BUILDID} {BUILDID}
*check changelog to insure correct repos were are being used to diff
cp ChangeLog-trunk-daily-* /srv/www/vhosts/trunk-daily/builds/trunk/{BUILDID}/.

*Check download.meego.com/trunk-daily/ for expected change

*If Testing-Daily
pushd /srv/www/vhosts/testing
cp -al trunk /srv/www/vhosts/testing-daily/builds/trunk/{BUILDID}
*copy sdk repo
cd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al sdk/target/repos/meego/trunk /srv/www/vhosts/testing-daily/builds/trunk/{BUILDID}/sdk
popd
cd ./bin
sh ./diff-testing-daily-repos {_LAST_BUILDID} {BUILDID}
*check changelog to insure correct repos were are being used to diff
cp ChangeLog-trunk-daily-* /srv/www/vhosts/testing-daily/builds/trunk/{BUILDID}/.

*Check download.meego.com/testing-daily/ for expected change

----

exit back to user

ssh 192.168.50.8 (AKA image server)

sudo su

cd

----

*AS USER root

'''*using SCREEN is preferred'''

screen -r

pushd /root/images/image-configurations

*For Tuesday Images
/root/create-daily.sh {BUILDID} 1 Trunk
*For trunk-daily Images
/root/create-daily.sh {BUILDID} 4 Trunk
*For testing-daily Images
/root/create-daily.sh {BUILDID} 5 Trunk

(use cntrl-a-d to detach the screen, and screen -r <id> to reattach)

'''IF GENERATING THE IMAGES FAILS!!'''

Make sure no MIC processes are left running before you attempt running the script.

*AS USER root

/usr/local/bin/cleanup-dead-mic

*Check to insure all images are created
cd ./{BUILDID}/core/images/
cd ./{BUILDID}/IVI/images/
cd ./{BUILDID}/handset/images/
cd ./{BUILDID}/netbook/images/

* RSYNC the images back to the download server

WEEKLY: rsync -avz <build_id> rsync://192.168.50.95/m2public/builds/<build_major_release_number>

TRUNK-DAILY: rsync -avz <build_id> rsync://192.168.50.95/trunk-daily/builds/<build_major_release_number>

TESTING-DAILY: rsync -avz <build_id> rsync://192.168.50.95/testing-daily/builds/<build_major_release_number>

e.g.
WEEKLY: rsync -avz 1.1.80.3.20101022.1 rsync://192.168.50.95/m2public/builds/1.1.80/
TRUNK-DAILY: rsync -avz trunk-daily-1.1.80.9.20101206.1 rsync://192.168.50.95/trunk-daily/builds/1.1.80/
TESTING-DAILY: rsync -avz testing-daily-1.1.80.9.20101206.1 rsync://192.168.50.95/testing-daily/builds/1.1.80/

----

* If Weekly Tuesday, sync the repos and images back to external site

exit back to downloads.meego.com to sync to repo.meego.com

on download.meego.com

sudo su repos

cd /home/repos/bin

sync-repos

* go though all bugs and features in change log and insure that the bugs
and features has been marked released.

User:Rolla/image-creation-notes

2010-12-14T00:07:28Z

Uhofemeier:

'''!!! FIRST CHECK IF ALL REPOS HAVE FINISHED BUILDING AND NOTHING FAILS TOO BADLY !!!'''

ssh download.meego.com

sudo su repos

cd

----

*AS USER repos

*If Tuesday
pushd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al builds/trunk/daily builds/trunk/{BUILDID}
popd
cd ./bin
sh diff-trunk-repos {_LAST_BUILDID} {BUILDID}
*check changelog to insure correct repos were are being used to diff
~repos/bin/sync-repos

*Check repo.meego.com/MeeGo/ for expected change

*If Trunk-Daily
pushd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al builds/trunk/daily /srv/www/vhosts/trunk-daily/builds/trunk/{BUILDID}
*copy sdk repo
cd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al sdk/target/repos/meego/trunk /srv/www/vhosts/trunk-daily/builds/trunk/{BUILDID}/sdk
popd
cd ./bin
sh ./diff-trunk-daily-repos {_LAST_BUILDID} {BUILDID}
*check changelog to insure correct repos were are being used to diff
cp ChangeLog-trunk-daily-* /srv/www/vhosts/trunk-daily/builds/trunk/{BUILDID}/.

*Check download.meego.com/trunk-daily/ for expected change

*If Testing-Daily
pushd /srv/www/vhosts/testing
cp -al trunk /srv/www/vhosts/testing-daily/builds/trunk/{BUILDID}
*copy sdk repo
cd /srv/www/vhosts/repo.m2.org/MeeGo
cp -al sdk/target/repos/meego/trunk /srv/www/vhosts/testing-daily/builds/trunk/{BUILDID}/sdk
popd
cd ./bin
sh ./diff-testing-daily-repos {_LAST_BUILDID} {BUILDID}
*check changelog to insure correct repos were are being used to diff
cp ChangeLog-trunk-daily-* /srv/www/vhosts/testing-daily/builds/trunk/{BUILDID}/.

*Check download.meego.com/testing-daily/ for expected change

----

exit back to user

ssh 192.168.50.8 (AKA image server)

sudo su

cd

----

*AS USER root

'''*using SCREEN is preferred'''

screen -r

pushd /root/images/image-configurations

*For Tuesday Images
../../create-daily.sh {BUILDID} 1 Trunk
*For trunk-daily Images
../../create-daily.sh {BUILDID} 4 Trunk
*For testing-daily Images
../../create-daily.sh {BUILDID} 5 Trunk

(use cntrl-a-d to detach the screen, and screen -r <id> to reattach)

'''IF GENERATING THE IMAGES FAILS!!'''

Make sure no MIC processes are left running before you attempt running the script.

*AS USER root

/usr/local/bin/cleanup-dead-mic

*Check to insure all images are created
cd ./{BUILDID}/core/images/
cd ./{BUILDID}/IVI/images/
cd ./{BUILDID}/handset/images/
cd ./{BUILDID}/netbook/images/

* RSYNC the images back to the download server

WEEKLY: rsync -avz <build_id> rsync://192.168.50.95/m2public/builds/<build_major_release_number>

TRUNK-DAILY: rsync -avz <build_id> rsync://192.168.50.95/trunk-daily/builds/<build_major_release_number>

TESTING-DAILY: rsync -avz <build_id> rsync://192.168.50.95/testing-daily/builds/<build_major_release_number>

e.g.
WEEKLY: rsync -avz 1.1.80.3.20101022.1 rsync://192.168.50.95/m2public/builds/1.1.80/
TRUNK-DAILY: rsync -avz trunk-daily-1.1.80.9.20101206.1 rsync://192.168.50.95/trunk-daily/builds/1.1.80/
TESTING-DAILY: rsync -avz testing-daily-1.1.80.9.20101206.1 rsync://192.168.50.95/testing-daily/builds/1.1.80/

----

* If Weekly Tuesday, sync the repos and images back to external site

exit back to downloads.meego.com to sync to repo.meego.com

on download.meego.com

sudo su repos

cd /home/repos/bin

sync-repos

* go though all bugs and features in change log and insure that the bugs
and features has been marked released.

User:Rolla/image-creation-notes

2010-11-22T19:53:40Z

Uhofemeier:

'''FIRST CHECK IF ALL REPOS HAVE FINISHED BUILDING AND NOTHING FAILS TOO BADLY!!'''

ssh download.meego.com
sudo su repos
cd
-Follow README.pub

++file located /home/repos on download.meego.com

----
README.pub

*AS USER repos

pushd /srv/www/vhosts/repo.m2.org/MeeGo

mv builds/trunk/preview/ builds/trunk/.preview-{_LAST_BUILDID}

cp -al builds/trunk/daily builds/trunk/preview

*If Tuesday
cp -al builds/trunk/daily builds/trunk/{BUILDID}
popd
cd ./bin
sh diff-trunk-repos .preview-{_LAST_BUILDID} preview
*check changelog to insure correct repos were are being used to diff
pushd /srv/www/vhosts/repo.m2.org/MeeGo
rm -rf builds/trunk/.preview-{_LAST_BUILDID}
~repos/bin/sync-repos

*If Friday
popd
cd ./bin
sh diff-trunk-repos {_LAST_BUILDID} preview
*check changelog to insure correct repos were are being used to diff
pushd /srv/www/vhosts/repo.m2.org/MeeGo
rm -rf builds/trunk/.preview-{_LAST_BUILDID}
~repos/bin/sync-repos

*Check *Check repo.meego.com/MeeGo/ for expected change

----

exit back to user
cp /home/repos/bin/Changelog-{REPO}-{REPO} /home/{USER}

ssh 192.168.50.8 (AKA image server)

sudo su
cd
-Follow README.pub

++file located /root**

----

README.images

*AS USER root

pushd /root/images/image-configurations

*For Tuesday Images
../../create-trunk.sh {BUILDID} 1 Trunk
*For Friday Images
../../create-trunk.sh {BUILDID} 2 Trunk

'''IF GENERATING THE IMAGES FAILS!!'''

Make sure no MIC processes are left running before you attempt running the script.

*AS USER root

/usr/local/bin/cleanup-dead-mic

*Check to insure all images are created
cd ./{BUILDID}/core/images/
cd ./{BUILDID}/IVI/images/
cd ./{BUILDID}/handset/images/
cd ./{BUILDID}/netbook/images/

rsync -avz <build_id> rsync://192.168.50.95/m2public/builds/<build_major_release_number>

e.g.
rsync -avz 1.1.80.3.20101022.1 rsync://192.168.50.95/m2public/builds/1.1.80/

----

exit back to downloads.meego.com to sync to repo.meego.com
on download.meego.com

sudo su repos

cd /home/repos/bin

sync-repos

mv Changelog-{REPO}-{REPO} changelogs

log out of download.meego.com

scp username@download.meego.com~/Change* .

take changelog of repos and clean them up by removing for example
setting up repos
setting up old repo
file:///srv/www/vhosts/repo.m2.org/MeeGo/builds/trunk/.preview-1.1.80.3.20101022.1/core/repos/source
setting up new repo
file:///srv/www/vhosts/repo.m2.org/MeeGo/builds/trunk/1.1.80.3.20101026.1/core/repos/source
performing the diff
which is generated by the script but not needed in the mail

send in mail

TO: meego-releases@meego.com
SUBJECT: MeeGo Package ChangeLog {LASTBUILD} -> {TODAY}
({_LAST_BUILDID}-{_NEW_BUILDID})

go though all bugs and features in change log and insure that the bugs
and features has been marked released.

Release Engineering/Plans/1.2

2010-10-25T22:44:28Z

Uhofemeier: Changed 2010 to 2011 for MM3: All planned features released...

== MeeGo 1.2 Release Plan (!!! DRAFT !!!)==

This plan is in '''DRAFT STATE'''. All content might be changed without any announcements.

{| cellpadding="5" cellspacing="0" border="1"
! Iteration !! Iteration<br/>start -- end<br/>dates !! MeeGo release focus !! Status<br/>URL !! Features<br/>Bugfixes<br/>Tasks
|-
| style="background-color:#ff9900" | 1.1.80.0
| 2010-09-30 -- 2010-10-06
| MM1: Trunk opened for 1.2 development on 2010-09-30.
|
| [[Release_Engineering/Plans/1.2/1.1.80.0|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.1
| 2010-10-07 -- 2010-10-13
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.1|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.2
| 2010-10-14 -- 2010-10-20
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.2|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.3
| 2010-10-21 -- 2010-10-27
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.3|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.4
| 2010-10-28 -- 2010-11-03
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.4|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.5
| 2010-11-04 -- 2010-11-10
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.5|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.6
| 2010-11-11 -- 2010-11-17
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.6|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.7
| 2010-11-18 -- 2010-11-24
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.7|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.8
| 2010-11-25 -- 2010-12-01
| MM2: Most intrusive changes delivered. Normal feature development continues after 2010-12-01. i18n code scans begin.
|
| [[Release_Engineering/Plans/1.2/1.1.80.8|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.9
| 2010-12-02 -- 2010-12-08
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.9|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.10
| 2010-12-09 -- 2010-12-15
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.10|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.11
| 2010-12-16 -- 2010-12-22
| MM2.5: checkpoint for features delivery
|
| [[Release_Engineering/Plans/1.2/1.1.80.11|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.12
| 2010-12-23 -- 2010-12-29
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.12|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.13
| 2010-12-30 -- 2011-01-05
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.13|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.14
| 2011-01-06 -- 2011-01-12
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.14|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.15
| 2011-01-13 -- 2011-01-19
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.15|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.0
| 2011-01-20 -- 2011-01-26
| MM3: All planned features released, Bugfixing for most of features starts after 2011-01-26, Possibility to integrate features that are late
|
| [[Release_Engineering/Plans/1.2/1.1.90.0|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.1
| 2011-01-27 -- 2011-02-02
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.1|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.2
| 2011-02-03 -- 2011-02-09
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.2|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.3
| 2011-02-10 -- 2011-02-16
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.3|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.4
| 2011-02-17 -- 2011-02-23
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.4|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.5
| 2011-02-24 -- 2011-03-02
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.5|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.6
| 2011-03-03 -- 2011-03-09
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.6|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.7
| 2011-03-10 -- 2011-03-16
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.7|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.8
| 2011-03-17 -- 2011-03-23
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.8|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.0
| 2011-03-24 -- 2011-03-30
| MM4: MeeGo 1.2 Release candidate 1 (preparation of marketing materials, to be published on 2011-03-30)
|
| [[Release_Engineering/Plans/1.2/1.1.99.0|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.1
| 2011-03-31 -- 2011-04-06
| MeeGo 1.2 Release candidate 2 (to be published on 2011-04-06)
|
| [[Release_Engineering/Plans/1.2/1.1.99.1|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.2
| 2011-04-07 -- 2011-04-13
| MeeGo 1.2 Release candidate 3 (to be published on 2011-04-13)
|
| [[Release_Engineering/Plans/1.2/1.1.99.2|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.3
| 2011-04-14 -- 2011-04-20
| MeeGo 1.2 Release candidate 4 (to be published on 2011-04-20)
|
| [[Release_Engineering/Plans/1.2/1.1.99.3|Details]]
|-
| style="background-color:#339966" | 1.2.0.0
| 2011-04-21 -- 2011-04-27
| MM5: MeeGo 1.2 Release for Core, Netbooks, Handsets, ... (General availability, release to web on 2011-04-27)
|
| [[Release_Engineering/Plans/1.2/1.2.0.0|Details]]
|}

== MeeGo 1.2 Features Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo Core OS Features,MeeGo Handset Features,MeeGo Netbook Features,MeeGo IVI Features
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Features&product=MeeGo+Connected+TV+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&product=MeeGo+IVI+Features&product=MeeGo+Netbook+Features&product=MeeGo+Tablet+Features&version=1.2&bug_severity=enhancement&format=table&action=wrap Detailed report in Featurezilla]

== MeeGo 1.2 Bugs Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo SDK,OS Base,OS Middleware,Handset User Experience,Netbook User Experience,Netbook IVI Experience
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Platform&product=Automotive+User+Experience&product=Handset+User+Experience&product=MeeGo+SDK&product=Netbook+User+Experience&product=OS+Base&product=OS+Middleware&version=1.2&format=table&action=wrap Detailed report in Bugzilla]

Release Engineering/Plans/1.2

2010-10-25T22:43:04Z

Uhofemeier:

== MeeGo 1.2 Release Plan (!!! DRAFT !!!)==

This plan is in '''DRAFT STATE'''. All content might be changed without any announcements.

{| cellpadding="5" cellspacing="0" border="1"
! Iteration !! Iteration<br/>start -- end<br/>dates !! MeeGo release focus !! Status<br/>URL !! Features<br/>Bugfixes<br/>Tasks
|-
| style="background-color:#ff9900" | 1.1.80.0
| 2010-09-30 -- 2010-10-06
| MM1: Trunk opened for 1.2 development on 2010-09-30.
|
| [[Release_Engineering/Plans/1.2/1.1.80.0|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.1
| 2010-10-07 -- 2010-10-13
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.1|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.2
| 2010-10-14 -- 2010-10-20
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.2|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.3
| 2010-10-21 -- 2010-10-27
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.3|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.4
| 2010-10-28 -- 2010-11-03
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.4|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.5
| 2010-11-04 -- 2010-11-10
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.5|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.6
| 2010-11-11 -- 2010-11-17
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.6|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.7
| 2010-11-18 -- 2010-11-24
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.7|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.8
| 2010-11-25 -- 2010-12-01
| MM2: Most intrusive changes delivered. Normal feature development continues after 2010-12-01. i18n code scans begin.
|
| [[Release_Engineering/Plans/1.2/1.1.80.8|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.9
| 2010-12-02 -- 2010-12-08
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.9|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.10
| 2010-12-09 -- 2010-12-15
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.10|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.11
| 2010-12-16 -- 2010-12-22
| MM2.5: checkpoint for features delivery
|
| [[Release_Engineering/Plans/1.2/1.1.80.11|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.12
| 2010-12-23 -- 2010-12-29
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.12|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.13
| 2010-12-30 -- 2011-01-05
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.13|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.14
| 2011-01-06 -- 2011-01-12
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.14|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.15
| 2011-01-13 -- 2011-01-19
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.15|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.0
| 2011-01-20 -- 2011-01-26
| MM3: All planned features released, Bugfixing for most of features starts after 2010-01-26, Possibility to integrate features that are late
|
| [[Release_Engineering/Plans/1.2/1.1.90.0|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.1
| 2011-01-27 -- 2011-02-02
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.1|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.2
| 2011-02-03 -- 2011-02-09
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.2|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.3
| 2011-02-10 -- 2011-02-16
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.3|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.4
| 2011-02-17 -- 2011-02-23
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.4|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.5
| 2011-02-24 -- 2011-03-02
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.5|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.6
| 2011-03-03 -- 2011-03-09
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.6|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.7
| 2011-03-10 -- 2011-03-16
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.7|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.8
| 2011-03-17 -- 2011-03-23
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.8|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.0
| 2011-03-24 -- 2011-03-30
| MM4: MeeGo 1.2 Release candidate 1 (preparation of marketing materials, to be published on 2011-03-30)
|
| [[Release_Engineering/Plans/1.2/1.1.99.0|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.1
| 2011-03-31 -- 2011-04-06
| MeeGo 1.2 Release candidate 2 (to be published on 2011-04-06)
|
| [[Release_Engineering/Plans/1.2/1.1.99.1|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.2
| 2011-04-07 -- 2011-04-13
| MeeGo 1.2 Release candidate 3 (to be published on 2011-04-13)
|
| [[Release_Engineering/Plans/1.2/1.1.99.2|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.3
| 2011-04-14 -- 2011-04-20
| MeeGo 1.2 Release candidate 4 (to be published on 2011-04-20)
|
| [[Release_Engineering/Plans/1.2/1.1.99.3|Details]]
|-
| style="background-color:#339966" | 1.2.0.0
| 2011-04-21 -- 2011-04-27
| MM5: MeeGo 1.2 Release for Core, Netbooks, Handsets, ... (General availability, release to web on 2011-04-27)
|
| [[Release_Engineering/Plans/1.2/1.2.0.0|Details]]
|}

== MeeGo 1.2 Features Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo Core OS Features,MeeGo Handset Features,MeeGo Netbook Features,MeeGo IVI Features
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Features&product=MeeGo+Connected+TV+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&product=MeeGo+IVI+Features&product=MeeGo+Netbook+Features&product=MeeGo+Tablet+Features&version=1.2&bug_severity=enhancement&format=table&action=wrap Detailed report in Featurezilla]

== MeeGo 1.2 Bugs Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo SDK,OS Base,OS Middleware,Handset User Experience,Netbook User Experience,Netbook IVI Experience
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Platform&product=Automotive+User+Experience&product=Handset+User+Experience&product=MeeGo+SDK&product=Netbook+User+Experience&product=OS+Base&product=OS+Middleware&version=1.2&format=table&action=wrap Detailed report in Bugzilla]

Release Engineering/Plans/1.2

2010-10-25T22:41:57Z

Uhofemeier:

== MeeGo 1.2 Release Plan (!!! DRAFT !!!)==

This plan is in '''DRAFT STATE'''. All content might be changed without any announcements.

{| cellpadding="5" cellspacing="0" border="1"
! Iteration !! Iteration<br/>start -- end<br/>dates !! MeeGo release focus !! Status<br/>URL !! Features<br/>Bugfixes<br/>Tasks
|-
| style="background-color:#ff9900" | 1.1.80.0
| 2010-09-30 -- 2010-10-06
| MM1: Trunk opened for 1.2 development on 2010-09-30.
|
| [[Release_Engineering/Plans/1.2/1.1.80.0|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.1
| 2010-10-07 -- 2010-10-13
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.1|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.2
| 2010-10-14 -- 2010-10-20
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.2|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.3
| 2010-10-21 -- 2010-10-27
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.3|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.4
| 2010-10-28 -- 2010-11-03
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.4|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.5
| 2010-11-04 -- 2010-11-10
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.5|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.6
| 2010-11-11 -- 2010-11-17
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.6|Details]]
|-
| style="background-color:#ff9900" | 1.1.80.7
| 2010-11-18 -- 2010-11-24
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.7|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.8
| 2010-11-25 -- 2010-12-01
| MM2: Most intrusive changes delivered. Normal feature development continues after 2011-12-01. i18n code scans begin.
|
| [[Release_Engineering/Plans/1.2/1.1.80.8|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.9
| 2010-12-02 -- 2010-12-08
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.9|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.10
| 2010-12-09 -- 2010-12-15
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.10|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.11
| 2010-12-16 -- 2010-12-22
| MM2.5: checkpoint for features delivery
|
| [[Release_Engineering/Plans/1.2/1.1.80.11|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.12
| 2010-12-23 -- 2010-12-29
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.12|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.13
| 2010-12-30 -- 2011-01-05
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.13|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.14
| 2011-01-06 -- 2011-01-12
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.14|Details]]
|-
| style="background-color:#ffff00" | 1.1.80.15
| 2011-01-13 -- 2011-01-19
|
|
| [[Release_Engineering/Plans/1.2/1.1.80.15|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.0
| 2011-01-20 -- 2011-01-26
| MM3: All planned features released, Bugfixing for most of features starts after 2010-01-26, Possibility to integrate features that are late
|
| [[Release_Engineering/Plans/1.2/1.1.90.0|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.1
| 2011-01-27 -- 2011-02-02
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.1|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.2
| 2011-02-03 -- 2011-02-09
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.2|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.3
| 2011-02-10 -- 2011-02-16
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.3|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.4
| 2011-02-17 -- 2011-02-23
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.4|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.5
| 2011-02-24 -- 2011-03-02
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.5|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.6
| 2011-03-03 -- 2011-03-09
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.6|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.7
| 2011-03-10 -- 2011-03-16
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.7|Details]]
|-
| style="background-color:#99cc00" | 1.1.90.8
| 2011-03-17 -- 2011-03-23
|
|
| [[Release_Engineering/Plans/1.2/1.1.90.8|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.0
| 2011-03-24 -- 2011-03-30
| MM4: MeeGo 1.2 Release candidate 1 (preparation of marketing materials, to be published on 2011-03-30)
|
| [[Release_Engineering/Plans/1.2/1.1.99.0|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.1
| 2011-03-31 -- 2011-04-06
| MeeGo 1.2 Release candidate 2 (to be published on 2011-04-06)
|
| [[Release_Engineering/Plans/1.2/1.1.99.1|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.2
| 2011-04-07 -- 2011-04-13
| MeeGo 1.2 Release candidate 3 (to be published on 2011-04-13)
|
| [[Release_Engineering/Plans/1.2/1.1.99.2|Details]]
|-
| style="background-color:#00ff00" | 1.1.99.3
| 2011-04-14 -- 2011-04-20
| MeeGo 1.2 Release candidate 4 (to be published on 2011-04-20)
|
| [[Release_Engineering/Plans/1.2/1.1.99.3|Details]]
|-
| style="background-color:#339966" | 1.2.0.0
| 2011-04-21 -- 2011-04-27
| MM5: MeeGo 1.2 Release for Core, Netbooks, Handsets, ... (General availability, release to web on 2011-04-27)
|
| [[Release_Engineering/Plans/1.2/1.2.0.0|Details]]
|}

== MeeGo 1.2 Features Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo Core OS Features,MeeGo Handset Features,MeeGo Netbook Features,MeeGo IVI Features
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Features&product=MeeGo+Connected+TV+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&product=MeeGo+IVI+Features&product=MeeGo+Netbook+Features&product=MeeGo+Tablet+Features&version=1.2&bug_severity=enhancement&format=table&action=wrap Detailed report in Featurezilla]

== MeeGo 1.2 Bugs Status ==
{{#bugzilla:
|columns=id,status,to,severity,version,summary
|product=MeeGo SDK,OS Base,OS Middleware,Handset User Experience,Netbook User Experience,Netbook IVI Experience
|version=1.2
|bar=status
|group=product
}}

[http://bugs.meego.com/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=product&query_format=report-table&classification=MeeGo+Platform&product=Automotive+User+Experience&product=Handset+User+Experience&product=MeeGo+SDK&product=Netbook+User+Experience&product=OS+Base&product=OS+Middleware&version=1.2&format=table&action=wrap Detailed report in Bugzilla]