(→Team) |
Uhofemeier (Talk | contribs) |
||
| Line 24: | Line 24: | ||
* [[Release_Engineering/Release_Timeline|Release lifecycle timeline]] | * [[Release_Engineering/Release_Timeline|Release lifecycle timeline]] | ||
* [[Release_Engineering/Process|MeeGo release process]] | * [[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/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]] | ||
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 |