Martin Michlmayr wrote: > * Joey Hess <joeyh@debian.org> [2004-05-14 00:46]: > > We could use criteria like these: > > > > - successful installation reports with on any arches the change affects > > I'm not sure of the meaning "any" here. If I make a generic change > (say, to mdcfg) which affects all arches, but all in the same way, it > should be enough to get it tested on one or two arches. Is this > correct? Just to clarify. Yes, I think so. Although it's easy to be too permissive here and miss an interaction that breaks one arch. > > Some other changes that happen as a consequence of doing things this way: > > - The d-i images in the debian-installer package should be built > > against the udebs in sarge, not unstable, though we will want > > to keep the daily builds built against sarge. > > Should we keep separate branches for this? Or where do I make a > change that will build against sid but not sarge? Currently we're using trunk for that; the current debian-installer package will not build against sarge. We can open a new branch for beta5 if we need to. > Also, it's not clear from your mail _when_ this testing propogation > happens. Only right before a new beta release is made, or can I ask > for a udeb to move to testing at any time? > > Basically, how I understand this is that I have to argue that my udeb > should move to testing, and I have to show that it won't break > anything. I think this sounds fair enough. Right, we can start propigation at any time, in fact we already have. -- see shy jo
Attachment:
signature.asc
Description: Digital signature