From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Veillard Subject: Re: [libvirt] Re: [Qemu-devel] Changing the QEMU svn VERSION string Date: Tue, 7 Apr 2009 11:03:22 +0200 Message-ID: <20090407090322.GC31447@redhat.com> References: <49DABC83.7010608@codemonkey.ws> <49DB0A6C.9080200@redhat.com> Reply-To: veillard@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: libvir-list@redhat.com, qemu-devel@nongnu.org, kvm-devel To: Gerd Hoffmann , Anthony Liguori Return-path: Content-Disposition: inline In-Reply-To: <49DB0A6C.9080200@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com List-Id: kvm.vger.kernel.org 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 ;-) Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/