From mboxrd@z Thu Jan  1 00:00:00 1970
From: Henning Sprang <henning@sprang.de>
Subject: xen versioning scheme
Date: Fri, 05 May 2006 23:44:12 +0200
Message-ID: <445BC72C.2020906@sprang.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hi,
I realized that the changes in xen versions between minor versions 3.0.1 
and 3.0.2 seem to be quite big. One example seems to be API changes as 
big as pci passthrough (I just read about it but didn't test that) and 
that the linux kernel configs seem to be quite different, at least in 
the xen section, probably also in the rest.

So I wonder why such big changes are only minor version numbers.

Is there some versioning scheme for the xen releases?

Henning