On Sat, Mar 28, 2020 at 02:11:02PM +0100, David Runge wrote: > On 2019-11-11 09:40:14 (-0300), Giancarlo Razzolini via arch-dev-public wrote: > > But, we still don't have anyone wanting to become the actual > > maintainer of archiso to help implement these changes. > > I'd be up for it. I have some ideas around certain possible test > scenarios in regards to packer and ansible already. > > What is currently still unclear to me is how the archiso and bootstrap > images on our download page are exactly generated from archiso (the > actual specific calls) and whether a semi-automated way of doing that > exists (I guess this question is aimed towards Pierre). > > I would like to automate this as far as possible and make this more > transparent when maintaining archiso. > > How do we go on from here? > > Best, > David > > -- > https://sleepmap.de
Hi, just a general idea, but wouldn't it make sense to revive the arch-releng mailing list a bit + found a release engineering team? We got a few additions to our monthly releases: * Arch Linux Docker * Arch Linux Vagrant Boxes * Arch Linux Cloud Images (soon) * Arch Linux Tarball Would be cool, if we could manage to revive the #archlinux-releng channel on freenode, revive the mailing list and maybe even have weekly meetings, like the devops team has. Just my 2 cents, chris
signature.asc
Description: PGP signature
