From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juan Quintela Subject: KVM call minutes for November 29 Date: Tue, 29 Nov 2011 16:51:14 +0100 Message-ID: <8762i3nczx.fsf@trasno.mitica> Reply-To: quintela@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Developers qemu-devel , KVM devel mailing list Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org Plans for 1.0 - rc4 should be the last release - should ship 1.0 on Thrusday Merge window start on Monday How to handle stable tree, getting a stable team? - Justin: he don't do schedules for releases because it depends on when patches arrive. - Adding a list for stable patches instead of more maintainers? Next release? - 6 month long also? Anthony: discuss it next week * think about it, and do proposals for next week call Update on QOM - Dynamic propierties for qdev - change types on qdev without touching all the tree several times Test infraestructure - Using a mini-os as an external process to be able to use libc and things like that. Sandboxing and other languages - sandboxing difficult - embedding a language (python?), that would make doing the easy devices emulation really easy How to do high level stuff? - python? Maintainer not responsive: - MIPS as an example, what to do. - In the specific case of MIPS, we haven't had a maintaner since Thiemo - If you feel that a subsystem is not being maintained, just make noise on the list See you next week.