[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [xen-unstable test] 17914: tolerable FAIL
On 07/05/13 15:20, Jan Beulich wrote:
On 07.05.13 at 16:16, George Dunlap <george.dunlap@xxxxxxxxxxxxx> wrote:
On 07/05/13 15:12, Jan Beulich wrote:
On 07.05.13 at 12:43, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
George Dunlap writes ("Re: [Xen-devel] [xen-unstable test] 17914: tolerable
FAIL"):
It looks like this passed all the tests -- it seems like a good
candidate for RC0 (or RC1, whatever we want to call it).
It looks like we still need to update some sonames. See patch below.
Also, do we want to update the version number in the README ? I think
we probably do.
I have tagged the qemu-xen-traditional tree with xen-4.3.0-rc1.
Stefano, please make an appropriate tag in qemu-xen-upstream.
We then need to update xen.git's Config.mk to refer to those tags.
Ian, I see you also tagged the Xen tree, but unfortunately without
updating the hypervisor revision to -rc1? Was that intentional? It's
not a dramatic problem (and I don't see a need to withdraw and
redo the tag), but maybe worth an addition to the checklist.
George, am I taking it right that with the tagging of RC1 the tree
freeze is over, and I can commit the few fixes that accumulated
over the last couple of days? Or should I wait until the tagged
commit got pushed too?
I wrote in a different e-mail "The tree is now open for commits again",
but maybe you missed it because it was after the bit about the RTC bug.
No, I'm sorry for the noise:, I should have read _all_ xen-devel mails
before replying to this one.
Oh, right -- fair enough. :-) The benefit of a separate e-mail is that
it catches people's eye who haven't been following the thread; the cost
is that there's a disconnect in the conversation...
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
