From: Anthony Liguori <anthony@codemonkey.ws>
To: veillard@redhat.com
Cc: libvir-list@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org
Subject: Re: [libvirt] Re: [Qemu-devel] Changing the QEMU svn VERSION string
Date: Tue, 07 Apr 2009 08:52:46 -0500 [thread overview]
Message-ID: <49DB5AAE.8050205@codemonkey.ws> (raw)
In-Reply-To: <20090407090322.GC31447@redhat.com>
Daniel Veillard wrote:
> On Tue, Apr 07, 2009 at 10:10:20AM +0200, Gerd Hoffmann wrote:
>
>> Hi,
>>
>>
>>> I'd like to update the VERSION string in QEMU's svn tree. Right now,
>>> it's 0.10.0 and since we have a 0.10.2 release, that's somewhat confusing.
>>>
>>> I don't want to make it 0.11.0 either because that's not going to be
>>> reliable from a feature detection perspective. What I would like is to
>>> make it 0.11.0-devel or something similar to that.
>>>
>> Maybe 0.10.99 ? Or 0.10.90, leaving the door open to number the 0.11
>> beta / rc versions (if any) 0.10.9{1,2,3}?
>>
>
> Concur, we have no good way of representing something like 0.11.0-devel
> from an rpm Name-Version-Release and be sure it won't break down the
> road if we change our mind on the final naming scheme, while something
> like 0.10.90 convey the intent while still being compatible with the
> existing numbering scheme (plus it eventually forces you to release the
> new version ;-)
>
I think that's going to lead to even more confusion. While I'm inclined
to not greatly mind 0.10.99 for the development tree, when we do release
candidates for the next release, it's going to be 0.11.0-rc1. I don't
expect RPMs to ever be created from non-release versions of QEMU
provided we stick to our plan of frequent releases.
I still think libvirt should work with versions of QEMU/KVM built from
svn/git though. I think the only way to do that is for libvirt to relax
their version checks to accommodate suffixes in the form
major.minor.stable-foo.
Regards,
Anthony Liguori
> Daniel
>
>
next prev parent reply other threads:[~2009-04-07 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:37 [Qemu-devel] Changing the QEMU svn VERSION string Anthony Liguori
2009-04-07 8:10 ` Gerd Hoffmann
[not found] ` <20090407090322.GC31447@redhat.com>
2009-04-07 13:52 ` Anthony Liguori [this message]
2009-04-07 17:13 ` [libvirt] " Jamie Lokier
2009-04-08 6:35 ` Gerd Hoffmann
2009-04-07 17:58 ` Daniel Jacobowitz
2009-04-07 22:36 ` Paul Brook
2009-04-08 13:13 ` Anthony Liguori
2009-04-08 13:56 ` Jamie Lokier
2009-04-07 9:04 ` [Qemu-devel] " Daniel P. Berrange
2009-04-07 16:09 ` [Qemu-devel] " Andreas Färber
2009-04-07 16:29 ` M. Warner Losh
2009-04-08 21:10 ` Andreas Färber
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=49DB5AAE.8050205@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=veillard@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).