Hi Lee, Lee Garrett <[email protected]> writes:
> Hi everyone, > > I'm in the final stages of creating borgbackup 1.4.1-3 (some packaging fixes > and > adding autopkgtests), I'll upload it today or tomorrow and then also file an > unblock request. > > Greets, > Lee > Thank you for your work doing various cleanup. Are you aware that the release team may look at the diff and say "these are too many changes, so we're refusing the unblock"? In particular, how do you know that the proposed autopkgtests won't cause borgbackup to fall out of trixie due to new failing autopkgtests on arm64? Potentially requiring a second upload to fix the first, and a second upload...do you think that meets the criteria for the hard freeze? The principle is thus: we want to unblock the package people have been using and the one whose behaviour has data on buildd, reprobuilds, DebCI, etc. Changes that don't have supporting data from these sources introduce risk, even if they're good changes! :) I'm in the process of preparing a minimal fix to NEWS as well as documenting the upstream changes so that the release team can assess the potential risk of unblocking the release. I'll push to a debian/trixie branch. I will wait to upload until everyone hears back from you, because that's the collaborative approach. Regards, Nicholas
signature.asc
Description: PGP signature
