qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Jia Liu <proljc@gmail.com>, Juan Quintela <quintela@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Markus Armbruster <armbru@redhat.com>,
	"Peter A. G. Crosthwaite" <peter.crosthwaite@petalogix.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>
Subject: Re: [Qemu-devel] Plans for the hard feature freeze
Date: Thu, 21 Jun 2012 15:23:41 +0200	[thread overview]
Message-ID: <4FE3205D.7030301@suse.de> (raw)
In-Reply-To: <4FAC7038.1080800@suse.de>

Am 11.05.2012 03:49, schrieb Andreas Färber:
> Am 29.04.2012 20:57, schrieb Anthony Liguori:
>> We'll run this release much like the last one.  All bug fixing will
>> happen in master until 1.1 is released.  If you plan on maintaining a
>> subsystem tree while we're in feature freeze, please respond to this
>> note with information about your tree.
> 
> On Paolo's suggestion and with Anthony's blessing I have set up a
> qom-next tree:
> 
> T: git git://repo.or.cz/qemu/afaerber.git qom-next
> T: git http://repo.or.cz/r/qemu/afaerber.git qom-next
> W: http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/qom-next
> 
> This is intended as temporary solution to minimize conflicts between QOM
> refactorings or features during the Hard Freeze and to facilitate a
> quick and painless merge into master once the window for 1.2 opens.

Slightly later than anticipated (due to the early 1.1 release and some
fallout from the build system overhaul) everything that made it into
qom-next is now merged into qemu.git master.

The qom-next branch is therefore officially disbanded.
Any QOM patches should be based onto qemu.git master branch again.

Still open among the QOM-related series I had tracked are for example:
* Paolo's and my "realize" - pending semantics discussion
* Paolo's static properties generalization - depends on state in Object
* my QOM CPUState part 4 (field movements) - needs review apart from TLB
* Igor's x86 CPU APIC/reset refactoring - under review
* Juan's VMState series - how to attach VMSD to CPUClass/DeviceClass?
* Markus' floppy QOM'ification - initial RFC only

Thanks to everyone who supported this effort during the Freeze!

Regards,
Andreas

> Stefan, can you add this branch to the build bots please?
> 
> qom-next will track master as a patch queue, rebasing as necessary.
> So if you want to add a tag or find a patch is bogus, say so. :)
> 
> Regards,
> Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      parent reply	other threads:[~2012-06-21 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F9D8F2F.3090507@codemonkey.ws>
2012-05-11  1:49 ` [Qemu-devel] Plans for the hard feature freeze Andreas Färber
2012-05-11  2:00   ` Anthony Liguori
2012-06-21 13:23   ` Andreas Färber [this message]

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=4FE3205D.7030301@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=imammedo@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@petalogix.com \
    --cc=peter.maydell@linaro.org \
    --cc=proljc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).