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.
- 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.
- Alexander Kanevskiy is the MeeGo Core OS release manager, responsible for planning and producing core OS releases.
- Ulf Hofemeier is the MeeGo Handset UX release lead, responsible for planning and producing handset releases.
- Carsten Munk is responsible for maintaining the MeeGo releases on the Nokia N900 hardware platform.
Terms and conventions
Supported CPU architectures
Obsoleted CPU architectures
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