Hi Folks, I would like to raise some questions about do an early 0.1 release for Kata. Eric Cardona is working on provide some packaging tooling for Kata Containers. The tools are an automation to build packages in OBS[1]. Seems that OBS system does not allow to access to internet, this is something that is needed today to build a Kata Containers image. The image builder will pull some extra packages to build the rootfs and the agent to create it. One option we have is to pre-build the images we will ship before each release. The rest of the time if a developer want a fresh image with the latest Kata agent, it can be generated with a osbuilder scripts[2]. If you are agree with this approach, I would like to do early 0.1 release for kata containers. The steps would be. - Tag all the repositories with the version 0.1 (currently most of the have a file called VERSION that has the version 0.1) - Create a release in github with its proper releases notes. - In the agent github release, attach the images (raw and initrd) - The published images in the agent release will be used by the packaging. So I would like to as if is there any concern about do an early 0.1 release with the current kata state? For Clear Containers we had some scripts to automate most of the process we could Use them for kata (tagging, release notes generation, version bump in the projects files). Having the tags will help to tests the packaging of a kata release. This also may help us to identify gaps for a final 1.0 release. - Cheers! Carlos Venegas [1] https://build.opensuse.org/ [2] https://github.com/kata-containers/osbuilder