From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Repositories and build system Date: Thu, 7 May 2009 17:51:16 +0100 Message-ID: <4A031184.8030802@eu.citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: Yuji Shimada , Xen Developers , Ian Jackson , Keir Fraser , "Zhai, Edwin" List-Id: xen-devel@lists.xenproject.org Dan Magenheimer wrote: >>> "Pull and build all latest known stable components >>> that work with xen-unstable changeset 19314" >> That would require formal, machine-readable tracking of the >> inter-version dependencies. Since at the moment we can't reliably >> accidentally avoid introducing cross-version breakage I don't think we >> can reliably avoid buggy metadata either. > > Understood. But it is a big loss to be unable to do a bisect > search for a bug. With the proliferation of repositories > and components, it may become necessary to impose some discipline > to avoid the introduction of (undocumented) locksteps. > I agree. In fact I think we should start to write in clear letters when a commit breaks xen\qemu compatibility, specifying the required changeset in the other repository. We could formally introduce this practice with the 3.5 development cycle.