(→Release Process) |
(→Release Plans) |
||
| (6 intermediate revisions not shown) | |||
| Line 9: | Line 9: | ||
* '''[http://meego.com/users/Tgraydon Tracy Graydon]''' is the MeeGo IVI release lead, responsible for planning and producing IVI 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. | * '''[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 16: | Line 18: | ||
* '''armv7el''' - [[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) | * '''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 === | ||
| Line 22: | Line 27: | ||
== 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 | + | * [[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 32: | 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 == | ||
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 |
To contact the team, send email to the meego-releases@meego.com mailing list.