Meego Wiki
Views

Release Engineering

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Terms and conventions)
(→Release Plans)
 
(17 intermediate revisions not shown)
Line 3: Line 3:
== Team ==
== Team ==
-
* '''[http://meego.com/users/rolla Rolla Selbak]'''  is the head of the MeeGo release engineering team. She is responsible for the MeeGo release engineering process and code line policy, and for overseeing and supporting the planning and production of the MeeGo Core OS and device category-specific releases on supported hardware platforms, while managing the MeeGo release engineering 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/rolla Rolla Selbak]''' is the MeeGo Core OS release manager, responsible for planning and producing core OS 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 UX release lead, responsible for planning and producing handset 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.
 +
 
 +
To contact the team, send email to the [mailto:meego-releases@meego.com meego-releases@meego.com] [http://lists.meego.com/listinfo/meego-releases mailing list].
== Terms and conventions ==
== Terms and conventions ==
Line 11: Line 16:
=== Supported CPU architectures ===
=== 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)
* '''ia32''' - 32bit [[wikipedia:Intel Atom|Intel Atom]], [[wikipedia:Intel Core 2|Intel Core 2]] or better CPU (support for [[wikipedia:SSSE3|SSSE3]] is required)
-
* '''armv7l''' - [[wikipedia:ARM_architecture|ARM architecture]] version 7 compatible CPUs (Cortex-A8, Thumb-2, NEON, VPFv3, [[wikipedia:Endianness|Little-endian]])
+
* '''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 Versioning ===
* [[Release_Engineering/Release_Versioning|MeeGo Release and Builds Versioning]]
* [[Release_Engineering/Release_Versioning|MeeGo Release and Builds Versioning]]
-
 
-
== Release Content ==
 
-
 
-
For each supported category, release should contain:
 
-
 
-
* '''Repositories''' (for each supported category). Repositories contains:
 
-
** source and binary packages for supported architectures for that category
 
-
** debug packages for corresponding binary packages
 
-
** build counters of packages for different architectures should be synced (relsync)
 
-
** repository metadata (repo-md metadata, comps, ...)
 
-
* '''Images''' (for each supported category set of images and supported HW might vary). Images contains:
 
-
** filesystem image(s). flashable or usable in other way.
 
-
** source configuration files needed to re-create this images (e.g. ks file)
 
-
** log file which shows process of creating that image
 
-
** list of packages included in that image
 
-
** image specific documentation, e.g. flashing guides (optional)
 
-
** MANIFEST file which contains checksums for files in the image directory
 
-
* '''Release notes'''
 
-
** changed packages
 
-
** changes in features (new/removed)
 
-
** bugfixes information
 
-
** known issues
 
-
** location of the images
 
-
** list of supported hardware for those images
 
-
** links to all additional support information if needed
 
-
* '''QA information'''
 
-
** which image was tested on which HW.
 
-
** type of the tests.
 
-
** tests passrate
 
-
** highlights if necessary
 
== Release Process ==
== Release Process ==
-
* [[Release_Engineering/Release_Timeline|Release lifecycle timeline]]
+
* [[Release_Engineering/Release_Timeline|Release 6-month lifecycle timeline]]
* [[Release_Engineering/Process|MeeGo release process]]
* [[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/Submission_Checklist|Developer's checklist for code submissions]]
* [[Release_Engineering/Repo_List|Repos to use for MeeGo]]
* [[Release_Engineering/Repo_List|Repos to use for MeeGo]]
Line 57: Line 37:
* [[Release_Engineering/Plans/1.1|MeeGo 1.1 release planning]]
* [[Release_Engineering/Plans/1.1|MeeGo 1.1 release planning]]
* [[Release_Engineering/Plans/1.2|MeeGo 1.2 release planning]]
* [[Release_Engineering/Plans/1.2|MeeGo 1.2 release planning]]
 +
* [[Release_Engineering/Plans/1.3|MeeGo 1.3 release planning]]
== Downloads ==
== Downloads ==
Line 63: Line 44:
* [http://repo.meego.com/MeeGo/updates/ MeeGo Updates]
* [http://repo.meego.com/MeeGo/updates/ MeeGo Updates]
* [http://repo.meego.com/MeeGo/builds/ MeeGo development releases]
* [http://repo.meego.com/MeeGo/builds/ MeeGo development releases]
-
** [http://repo.meego.com/MeeGo/builds/1.0.80/ Development releases for upcoming 1.1 release]
 
[[Category:Release engineering]]
[[Category:Release engineering]]

Latest revision as of 21:04, 6 June 2011

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.

Contents

Team

  • 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.
  • Peter Zhu is the MeeGo Core OS release lead, responsible for planning and producing core OS releases.
  • Ulf Hofemeier is the MeeGo Handset release lead, responsible for planning and producing handset releases.
  • Praj Karur Mohan is the MeeGo Tablet release lead, responsible for planning and producing tablet releases.
  • Tracy Graydon is the MeeGo IVI release lead, responsible for planning and producing IVI releases.
  • Yin Yan is the MeeGo Netbook & TV release lead, responsible for planning and producing Netbook & TV releases.

To contact the team, send email to the meego-releases@meego.com mailing list.

Terms and conventions

Supported CPU architectures

  • ia32 - 32bit Intel Atom, Intel Core 2 or better CPU (support for SSSE3 is required)
  • armv7el - ARM architecture version 7 compatible CPUs (Cortex-A8, Thumb-2, NEON, VPFv3, Little-endian)
  • armv8el (OBS scheduler name), armv7hl (RPM base architecture) ARM architecture version 7 compatible CPUs, with hard-float ABI (VFPv3-D16, subarchitectures exist for NEON and Thumb2)

Build Infrastructure

Release Versioning

Release Process

Release Plans

Downloads

Retrieved from "http://wiki.meego.com/Release_Engineering"
Personal tools