Much of this covered things discussed elsewhere: * Allowing multiple versions of the tools to be installed at the same time * Getting rid of external builds
There was a long discussion about security patches, with the general proposal being that we should cut a point release for every security issue. One random thing was that xenstored apparently has an 'in-memory-only' option. Since xenstored can't actually be restarted ATM, and most distros seemed to put xenstored in a tmpfs for performance reasons, this should probably be the default. https://hackmd.io/vmacVBYbQiORJ9H4_a9Ivw # Xen on Distros design session * qemu / libxc dependency loop * build system needs "extras" turned off * xenstored / tmpfs / memory-only option? * Disabling auto-download in build system * WGET=/bin/false * Multiple version of Xen / tools? * Debian has co-install * Change some installation paths * /usr/lib/xen/4.11/... * /usr/bin/xl is a shell script * libfsimage is special * Don't need to downgrade to older tools * Gentoo has a ~~dumpster fire~~ something * A hack which stops the package manager to allow you to reboot the box halfway through * Security issues * Building from stable branch / staging branch * Doing a "point release" every XSA? * "Release from staging" is effectively a low-quality release * Idea: Always immediately release from staging? # Actions * [ ] Ian: Post a git branch of Debian co-install to xen-devel * [ ] George: Post systemd / selinux / xenstored patch * [ ] George, Ian: private osstest runs * [ ] VOLUNTEER: Propose / argue for a point release per XSA * [ ] VOLUNTEER: Improve release automation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
