Meego Wiki
Views

Release Engineering

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Release Content: added information to release content section)
m (→Release Content)
Line 25: Line 25:
For each supported category, release should contain:
For each supported category, release should contain:
-
* Repositories (for each supported category). Repositories contains:
+
* '''Repositories''' (for each supported category). Repositories contains:
** source and binary packages for supported architectures for that category
** source and binary packages for supported architectures for that category
** debug packages for corresponding binary packages
** debug packages for corresponding binary packages
** build counters of packages for different architectures should be synced (relsync)
** build counters of packages for different architectures should be synced (relsync)
** repository metadata (repo-md metadata, comps, ...)  
** repository metadata (repo-md metadata, comps, ...)  
-
* Images (for each supported category set of images and supported HW might vary). Images contains:
+
* '''Images''' (for each supported category set of images and supported HW might vary). Images contains:
** filesystem image(s). flashable or usable in other way.
** filesystem image(s). flashable or usable in other way.
** source configuration files needed to re-create this images (e.g. ks file)
** source configuration files needed to re-create this images (e.g. ks file)
Line 37: Line 37:
** image specific documentation, e.g. flashing guides (optional)
** image specific documentation, e.g. flashing guides (optional)
** MANIFEST file which contains checksums for files in the image directory
** MANIFEST file which contains checksums for files in the image directory
-
* Release notes
+
* '''Release notes'''
** changed packages
** changed packages
** changes in features (new/removed)
** changes in features (new/removed)
Line 45: Line 45:
** list of supported hardware for those images
** list of supported hardware for those images
** links to all additional support information if needed
** links to all additional support information if needed
-
* QA information
+
* '''QA information'''
** which image was tested on which HW.
** which image was tested on which HW.
** type of the tests.
** type of the tests.

Revision as of 22:00, 20 June 2010

Contents

Release Engineering

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

  • Terence Chen is the head of the MeeGo release engineering team. He 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.
  • Alexander Kanevskiy is the MeeGo Core OS release manager, responsible for planning and producing core OS releases.
  • Chris Ferron is the MeeGo Handset UX release manager, responsible for planning and producing handset releases.
  • Risto Lankinen is responsible for maintaining the ARM architecture-specific toolchain and libraries in MeeGo.
  • Harri Hakulinen is responsible for maintaining the MeeGo releases on the Nokia N900 hardware platform.

Terms and conventions

Supported CPU architectures

Release 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 Plans

Downloads

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