* [Qemu-devel] Any QEMU 2.8 release blockers? @ 2016-12-09 15:34 Stefan Hajnoczi 2016-12-13 10:01 ` Stefan Hajnoczi 0 siblings, 1 reply; 7+ messages in thread From: Stefan Hajnoczi @ 2016-12-09 15:34 UTC (permalink / raw) To: qemu-devel; +Cc: Peter Maydell Hi folks, How is QEMU 2.8.0-rc3 holding up? I'm not aware of release blockers. QEMU 2.8.0 will be released on Tuesday, December 13th if nothing comes up. It will be the -rc3 source tree. Stefan ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Any QEMU 2.8 release blockers? 2016-12-09 15:34 [Qemu-devel] Any QEMU 2.8 release blockers? Stefan Hajnoczi @ 2016-12-13 10:01 ` Stefan Hajnoczi 2016-12-13 21:04 ` Stefan Hajnoczi 0 siblings, 1 reply; 7+ messages in thread From: Stefan Hajnoczi @ 2016-12-13 10:01 UTC (permalink / raw) To: qemu-devel; +Cc: Peter Maydell On Fri, Dec 9, 2016 at 3:34 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote: > Hi folks, > How is QEMU 2.8.0-rc3 holding up? > > I'm not aware of release blockers. QEMU 2.8.0 will be released on > Tuesday, December 13th if nothing comes up. It will be the -rc3 > source tree. There have been no release blockers so I plan to tag QEMU 2.8.0 today (December 13th at 19:00 UTC). If something critical turns up please notify me on IRC (stefanha on #qemu irc.oftc.net). Thanks, Stefan ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Any QEMU 2.8 release blockers? 2016-12-13 10:01 ` Stefan Hajnoczi @ 2016-12-13 21:04 ` Stefan Hajnoczi 2016-12-13 21:33 ` Michael Roth 2016-12-13 21:39 ` Stefan Weil 0 siblings, 2 replies; 7+ messages in thread From: Stefan Hajnoczi @ 2016-12-13 21:04 UTC (permalink / raw) To: qemu-devel; +Cc: Peter Maydell, Michael Roth On Tue, Dec 13, 2016 at 10:01 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote: > On Fri, Dec 9, 2016 at 3:34 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote: >> Hi folks, >> How is QEMU 2.8.0-rc3 holding up? >> >> I'm not aware of release blockers. QEMU 2.8.0 will be released on >> Tuesday, December 13th if nothing comes up. It will be the -rc3 >> source tree. > > There have been no release blockers so I plan to tag QEMU 2.8.0 today > (December 13th at 19:00 UTC). > > If something critical turns up please notify me on IRC (stefanha on > #qemu irc.oftc.net). Mike Roth discovered a migration compatibility bug introduced by commit d1b4259f1ab18af24e6a297edb6a8f71691f3256 ("virtio-bus: Plug devices after features are negotiated"). The release will be delayed until this is resolved. Please check the mailing list for discussion. Mike is sending out a mail summarizing the bug. Stefan ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Any QEMU 2.8 release blockers? 2016-12-13 21:04 ` Stefan Hajnoczi @ 2016-12-13 21:33 ` Michael Roth 2016-12-13 21:39 ` Stefan Weil 1 sibling, 0 replies; 7+ messages in thread From: Michael Roth @ 2016-12-13 21:33 UTC (permalink / raw) To: Stefan Hajnoczi, qemu-devel; +Cc: Peter Maydell Quoting Stefan Hajnoczi (2016-12-13 15:04:24) > On Tue, Dec 13, 2016 at 10:01 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote: > > On Fri, Dec 9, 2016 at 3:34 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote: > >> Hi folks, > >> How is QEMU 2.8.0-rc3 holding up? > >> > >> I'm not aware of release blockers. QEMU 2.8.0 will be released on > >> Tuesday, December 13th if nothing comes up. It will be the -rc3 > >> source tree. > > > > There have been no release blockers so I plan to tag QEMU 2.8.0 today > > (December 13th at 19:00 UTC). > > > > If something critical turns up please notify me on IRC (stefanha on > > #qemu irc.oftc.net). > > Mike Roth discovered a migration compatibility bug introduced by > commit d1b4259f1ab18af24e6a297edb6a8f71691f3256 ("virtio-bus: Plug > devices after features are negotiated"). The release will be delayed > until this is resolved. > > Please check the mailing list for discussion. Mike is sending out a > mail summarizing the bug. I've posted a summary in the original patch thread: https://lists.gnu.org/archive/html/qemu-devel/2016-12/msg01862.html > > Stefan > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Any QEMU 2.8 release blockers? 2016-12-13 21:04 ` Stefan Hajnoczi 2016-12-13 21:33 ` Michael Roth @ 2016-12-13 21:39 ` Stefan Weil 2016-12-13 21:52 ` Stefan Hajnoczi 1 sibling, 1 reply; 7+ messages in thread From: Stefan Weil @ 2016-12-13 21:39 UTC (permalink / raw) To: Stefan Hajnoczi, qemu-devel; +Cc: Peter Maydell, Michael Roth On 12/13/16 22:04, Stefan Hajnoczi wrote: > On Tue, Dec 13, 2016 at 10:01 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote: >> On Fri, Dec 9, 2016 at 3:34 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote: >>> Hi folks, >>> How is QEMU 2.8.0-rc3 holding up? >>> >>> I'm not aware of release blockers. QEMU 2.8.0 will be released on >>> Tuesday, December 13th if nothing comes up. It will be the -rc3 >>> source tree. >> >> There have been no release blockers so I plan to tag QEMU 2.8.0 today >> (December 13th at 19:00 UTC). >> >> If something critical turns up please notify me on IRC (stefanha on >> #qemu irc.oftc.net). > > Mike Roth discovered a migration compatibility bug introduced by > commit d1b4259f1ab18af24e6a297edb6a8f71691f3256 ("virtio-bus: Plug > devices after features are negotiated"). The release will be delayed > until this is resolved. > > Please check the mailing list for discussion. Mike is sending out a > mail summarizing the bug. > > Stefan > Maybe you can update the po files before tagging the release. They currently no longer match the code (changed line numbers, new string "_Copy"). Long way: make install Short way: make -C po build Stefan ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Any QEMU 2.8 release blockers? 2016-12-13 21:39 ` Stefan Weil @ 2016-12-13 21:52 ` Stefan Hajnoczi 2016-12-14 6:31 ` [Qemu-devel] QEMU po files / translations (was: Any QEMU 2.8 release blockers?) Stefan Weil 0 siblings, 1 reply; 7+ messages in thread From: Stefan Hajnoczi @ 2016-12-13 21:52 UTC (permalink / raw) To: Stefan Weil; +Cc: qemu-devel, Peter Maydell, Michael Roth On Tue, Dec 13, 2016 at 9:39 PM, Stefan Weil <sw@weilnetz.de> wrote: > On 12/13/16 22:04, Stefan Hajnoczi wrote: >> >> On Tue, Dec 13, 2016 at 10:01 AM, Stefan Hajnoczi <stefanha@gmail.com> >> wrote: >>> >>> On Fri, Dec 9, 2016 at 3:34 PM, Stefan Hajnoczi <stefanha@gmail.com> >>> wrote: >>>> >>>> Hi folks, >>>> How is QEMU 2.8.0-rc3 holding up? >>>> >>>> I'm not aware of release blockers. QEMU 2.8.0 will be released on >>>> Tuesday, December 13th if nothing comes up. It will be the -rc3 >>>> source tree. >>> >>> >>> There have been no release blockers so I plan to tag QEMU 2.8.0 today >>> (December 13th at 19:00 UTC). >>> >>> If something critical turns up please notify me on IRC (stefanha on >>> #qemu irc.oftc.net). >> >> >> Mike Roth discovered a migration compatibility bug introduced by >> commit d1b4259f1ab18af24e6a297edb6a8f71691f3256 ("virtio-bus: Plug >> devices after features are negotiated"). The release will be delayed >> until this is resolved. >> >> Please check the mailing list for discussion. Mike is sending out a >> mail summarizing the bug. >> >> Stefan >> > > Maybe you can update the po files before tagging the release. > They currently no longer match the code (changed line numbers, > new string "_Copy"). > > Long way: make install > Short way: make -C po build I've sent a patch to the list and CCed you. I ran make -C po update. Weird that the line numbers are hardcoded in the .po file format. An addr2line type tool would have been better to avoid the constant outdated line numbers. That said, I don't know anything about how gettext is designed... Stefan ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Qemu-devel] QEMU po files / translations (was: Any QEMU 2.8 release blockers?) 2016-12-13 21:52 ` Stefan Hajnoczi @ 2016-12-14 6:31 ` Stefan Weil 0 siblings, 0 replies; 7+ messages in thread From: Stefan Weil @ 2016-12-14 6:31 UTC (permalink / raw) To: Stefan Hajnoczi; +Cc: qemu-devel, Peter Maydell, Michael Roth On 12/13/16 22:52, Stefan Hajnoczi wrote: > I've sent a patch to the list and CCed you. I ran make -C po update. > > Weird that the line numbers are hardcoded in the .po file format. An > addr2line type tool would have been better to avoid the constant > outdated line numbers. That said, I don't know anything about how > gettext is designed... xgettext has an optional parameter --no-location which suppresses the comments with filename:line. All QEMU texts currently come from gtk.c, so that information is not very useful. We could try running with --no-location for the next release. Even then the po files need a little bit more maintenance: several texts don't have translations. And of course there are more strings than those in gtk.c which could be translated, e. g. the help texts, monitor output, error messages, ... Stefan ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-12-14 6:31 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2016-12-09 15:34 [Qemu-devel] Any QEMU 2.8 release blockers? Stefan Hajnoczi 2016-12-13 10:01 ` Stefan Hajnoczi 2016-12-13 21:04 ` Stefan Hajnoczi 2016-12-13 21:33 ` Michael Roth 2016-12-13 21:39 ` Stefan Weil 2016-12-13 21:52 ` Stefan Hajnoczi 2016-12-14 6:31 ` [Qemu-devel] QEMU po files / translations (was: Any QEMU 2.8 release blockers?) Stefan Weil
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.