| Line 11: | Line 11: | ||
For now, comments to the meego-dev mailing list, until we get kicked off! | For now, comments to the meego-dev mailing list, until we get kicked off! | ||
| + | |||
| + | == Schedule MeeGo 1.1 Compliance == | ||
| + | |||
| + | * Preliminary compliance package list (i.e. the minimum set of required on-device packages) - week of September 20 | ||
| + | * Next Rev of compliance spec including profiles - week of September 27 | ||
| + | * First version of compliance tools for distribution / device - week of October 4th | ||
| + | * First version of compliance tools for applications - week of October 11th | ||
| + | * Final compliance package list and spec for 1.1 release, and tools updates as needed - with the MeeGo 1.1 release end of October | ||
The MeeGo compliance program is designed to make sure things stay compatible, such that the devices supporting a particular MeeGo version can run the same software, and so that app developers know how to build software which will run across the family.
A part of the program is the Compliance Specification, which describes the rules and requirements for complying. There's more to the program (trademark licensing, application process, etc.) which will be added later.
Here's an initial draft of the specification for public comment. This is intended to match the MeeGo 1.1 release, so it uses a similar numbering scheme.
For now, comments to the meego-dev mailing list, until we get kicked off!