Hi all, Great job on the BuildStream 2.0 release!
Now that 2.0 is out, I wanted to follow up with a discussion about how we want to expose that in our Docker images. At present, our `latest` tag comes with BuildStream 1. However, by our own defintion, the `latest` tag is supposed to track the latest stable release, which would now be BuildStream 2. This can be a breaking changes for some users of this image. So, I wanted to check here to see if anyone would have any objections, or would want more time, before doing so. For folks who still need BuildStream 1, the `bst1` tag exists that will continue to track the 1.x series. Parallel to that, there's now also a `bst2` tag [0], that will track the 2.x series and the corresponding plugins [1]. This image is also fresh off the press, so it'd be great you can help test it in the wild. While I have tested it on some test projects, that may not be quite extensive. Any thoughts? If no one objects in the next couple weeks or so, I'll assume that people can live with this change. Cheers, Chandan [0]: https://hub.docker.com/layers/buildstream/buildstream/bst2/images/sha256-573ed6ff1121d87cec32fc70320b0dcab91df36694b2aa208b970208f3eb8bd6 [1]: As a sidenote, it will be good if we can fix the PyPI publishing of https://gitlab.com/BuildStream/bst-plugins-experimental so that we don't have to install it via git.
