1 - Example usage/proposed project structure description
2 - List only top-level target components
3 - matrix pull/reset - fail if the checked-out branch differs from the
4 component configuration
5 - matrix reset [--force] - new command for automatically changing the branch
6 (and nuking local changes when forced) of a checked-out component
7 - Standardized version tag for generating source dist and manifests etc.
8 - Mechanism and metadata for checking new upstream versions of components
9 - Component should be able to force make -j1
10 - API documentation build mode
11 - Clean up lua-legacy metadata format
12 - Internal Python API documentation
13 - Command for listing all available components in the roots
19 - Fix installation in SB2
20 - Inject dependencies to packages (for automatic SB2 target setup)
21 - Use target-specific build directory for components which support it to enable
22 fast rebuilds when working with multiple targets
28 - Installed file list generation
29 - Add include/exclude rules to component metadata
30 - Debian package creation using file list, include/exclude rules and fakedb
31 - Rootfs creation using the packaging information
32 - Move device/directory creation from rootfs creation to a component
33 - Rootfs generation should support generating multiple image formats at once