All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Developers qemu-devel <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>
Subject: KVM call minutes for November 29
Date: Tue, 29 Nov 2011 16:51:14 +0100	[thread overview]
Message-ID: <8762i3nczx.fsf@trasno.mitica> (raw)


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.

WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: Developers qemu-devel <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>
Subject: [Qemu-devel] KVM call minutes for November 29
Date: Tue, 29 Nov 2011 16:51:14 +0100	[thread overview]
Message-ID: <8762i3nczx.fsf@trasno.mitica> (raw)


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.

             reply	other threads:[~2011-11-29 15:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 15:51 Juan Quintela [this message]
2011-11-29 15:51 ` [Qemu-devel] KVM call minutes for November 29 Juan Quintela
2011-11-29 16:59 ` Avi Kivity
2011-11-29 16:59   ` [Qemu-devel] " Avi Kivity
2011-11-29 19:10   ` Markus Armbruster
2011-11-29 19:10     ` Markus Armbruster
2011-11-30  1:18     ` Juan Quintela
2011-11-30  1:18       ` [Qemu-devel] " Juan Quintela
2011-12-01  9:32     ` Avi Kivity
2011-12-01  9:32       ` Avi Kivity
2011-11-29 22:59   ` Anthony Liguori
2011-11-29 22:59     ` Anthony Liguori
2011-11-30  9:22     ` Alon Levy
2011-11-30  9:22       ` [Qemu-devel] " Alon Levy
2011-11-30  9:54       ` Daniel P. Berrange
2011-11-30 13:54         ` Anthony Liguori
2011-11-30 13:54           ` Anthony Liguori
2011-11-30 14:35           ` Alon Levy
2011-11-30 14:35             ` Alon Levy
2011-11-30 14:38             ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8762i3nczx.fsf@trasno.mitica \
    --to=quintela@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.