On November 7, 2025 8:48:07 AM EST, Christian Hesse <[email protected]> wrote: > Hello everybody, > > for some time I used to push rc release for some packages (namely systemd & > util-linux) to core-testing. This broke once, when a package was built > against that rc release and thus did depend on new symbols, then finally was > moved before the package it was built against. > > After that I pushed all the rc releases to a public personal repository, > anybody interested could test from there. But I think the audience was a lot > smaller, and last systemd release revealed some unexpected regressions > *after* final release. That situation is not any better, especially when > rc releases in Arch were a major factor in finding regressions early. > > At Arch Summit 2025 we had a chat about that situation and discussed several > ideas. In the end we came up with one reasonable solution: > We should introduce new repositories [core-unstable] and [extra-unstable] for > this kind of testing. People would still have to enable these repositories, > but I guess chances are higher than for my personal repository. > > I guess we have three places that need to be touched: > > * create repositories on servers (-> DevOps) > * dbscripts > * devtools > > Anything more?
Would -unstable also go through the sign off process? If so: - arch-signoff - archweb > Feedback is welcome, same for other ideas - this is not set in stone and I am > open for anything that works for me/us. Thanks! -- Best, Daniel <https://danielcapella.com>
