* Re: [Qemu-devel] Plans for the hard feature freeze
[not found] <4F9D8F2F.3090507@codemonkey.ws>
@ 2012-05-11 1:49 ` Andreas Färber
2012-05-11 2:00 ` Anthony Liguori
2012-06-21 13:23 ` Andreas Färber
0 siblings, 2 replies; 3+ messages in thread
From: Andreas Färber @ 2012-05-11 1:49 UTC (permalink / raw)
To: qemu-devel, Stefan Hajnoczi
Cc: Peter Maydell, Juan Quintela, Michael Roth, Anthony Liguori,
Igor Mammedov, Paolo Bonzini
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.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Plans for the hard feature freeze
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
1 sibling, 0 replies; 3+ messages in thread
From: Anthony Liguori @ 2012-05-11 2:00 UTC (permalink / raw)
To: Andreas Färber
Cc: Peter Maydell, Juan Quintela, Stefan Hajnoczi, Michael Roth,
qemu-devel, Paolo Bonzini, Igor Mammedov
On 05/10/2012 08:49 PM, Andreas Färber wrote:
> 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:
Thanks Andreas!
Regards,
Anthony Liguori
>
> 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.
>
> 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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Plans for the hard feature freeze
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
1 sibling, 0 replies; 3+ messages in thread
From: Andreas Färber @ 2012-06-21 13:23 UTC (permalink / raw)
To: qemu-devel
Cc: Peter Maydell, Jia Liu, Juan Quintela, Jan Kiszka, Michael Roth,
Markus Armbruster, Peter A. G. Crosthwaite, Anthony Liguori,
Paolo Bonzini, Igor Mammedov, Guan Xuetao
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-06-21 13:24 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 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).