It all started three years ago, when Tristan van Berkom demoed Buildstream as a potential replacement for JHBuild, GNOME Continuous and flatpak manifests.
A few months later, in early 2018, the release team started using it for releases. And in the same year Michael Catanzaro concluded that it wasn't ready for developers.
Fast forward to today, we have successfully replaced GNOME Continuous, but developers are still using flatpak (for apps) and JHBuild (for desktop components) to build GNOME.
This talk will go about giving another chance to Buildstream as a developer tool. I'll present suggested workflows for both app and desktop components developments, and the remaining pain points. I'll also touch a bit on the upcoming release of Buildstream 2.0.
|Level of Difficulty||Technical|