We had a lot of excitement last April when we launched the 1.0 version of the Yocto Project. We celebrated a little while, and then got ourselves back to work to begin working on the next release of the Yocto Project, due in October.

The Yocto Project Advisory Board made a recommendation that we keep things simple on naming this next release. So we're calling it "version 1.1." We laid out our proposed features at the Linux Foundation Collaboration Summit with those who were interested in collaborating, and we started work on design and cutting code.

This week we released our first development milestone for the 1.1 release. Just as a reminder, we have three main development milestones which serve as synch points for features. For each of these we have a development window, and then a stabilization phase and a QA pass. We don't do extensive validation of these, but we do enough to understand the level of functionality we have at each of these points in the project, to prevent surprises at the end.

If you want to track our development progress, you can always look at our schedule wiki page which we keep up to date at a very close level from week to week.

As I said, our M1 release came out this week, as announced by Beth Flanagan. In the M1 milestone, we have a number of features complete and demonstratable:

  • A rebranding of many areas of the project to reflect that we derive from the "OpenEmbedded Core" upstream project. This means for example that instead of doing "bitbake poky-image-sato," you would instead build the "core-image-sato" target.
  • We have shifted our tool chain to GCC v4.6. We try to do this early in the development cycle, to ensure that any issues have been shaken out before release.
  • We have some of our core packages upgraded.
  • Our license infrastructure has been upgraded to provide more consistency and quality, and our LICENSE parser has been upgraded.

We have a lot more work ahead of us. I'm very excited about the progress on multi-lib and the Hob and other features which we have ahead of us, as well as the complete set of package upgrades.

If you are interested in the new M1 bits and want to try them out, now would be a great time to dig into them.