Hi, Adam D. Barratt <[email protected]> (2018-07-10): > On Tue, 2018-07-10 at 02:36 +0200, Cyril Brulebois wrote: > > I'm not sure I'll be able to run tests (with a hacked archive due to > > the udebs being in s-p-u) before late evenings of Tuesday or > > Wednesday. > > Should I upload right away, so that we can build d-i and d-i-n-i > > first, and eventually not include them for the point release if > > subsequent tests show regressions? > > > > That would get builds out of your way, while leaving us an > > opportunity to abort their inclusion if regressions are detected? > > Sure, that seems like a reasonable plan to me; thanks.
In the end I've been out longer than I thought I would, so I only managed to give it a go during the night. Being bugged by the perspective of only build-testing d-i before the upload, I've gone ahead with the whole “hack an archive” game, and it looks like test cases like plain disk, encrypted LVM, plain disk with XFS don't regress. Those usually let us (dis)cover kernel-related fun, so I guess green lights means we can merge this kernel ABI bump without too many second thoughts. If that upload gets accepted and built during the day, I can probably take care of dini this evening. Cheers, -- Cyril Brulebois ([email protected]) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
