From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: 3.0.3 freeze Date: Mon, 28 Aug 2006 16:21:14 +0100 Message-ID: <20060828152114.GD862@redhat.com> References: <20060828145839.GB862@redhat.com> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline 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: Keir Fraser Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, Aug 28, 2006 at 04:08:00PM +0100, Keir Fraser wrote: > On 28/8/06 3:58 pm, "Daniel P. Berrange" wrote: > > > Is this change going into 3.0.3, or is xen-unstable now reflecting the > > development for 3.0.4 ? We've got the means to support this new format > > for hypercalls in libvirt, while keeping compatability for old API > > (detectable at runtime), but if its not going to 3.0.3 we can postpone > > this dev work... > > All bug fixing is going on in the unstable tree: there has been no fork. I'm > now done with major refactorings (domctl/sysctl on Friday; shadow2->shadow > today). I wanted those in before 3.0.3 because, although large, they are > unlikely to break anything, and it is a pain to move patches across branches > after a fork when only one branch has a major code reorg applied to it. I > hope you'll agree that the hypercall refactoring has resulted in a cleaner > interface than the old dom0_ops, and that it is a useful goal to allow the > dom0 kernel and tools interfaces to evolve separately from each other. Yes, the re-factoring does look like a good idea from a long term maintenance POV - it just caught us a little by surprise ! Thanks for clarifying the current branch situation. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|