xen versioning scheme

xen versioning scheme

[Henning Sprang]

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

xen versioning scheme

[Henning Sprang]

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 theyr aren't re-usable
between these versions without major diffing hassles.

I admit, it isn't possible to got to Kernel 2.6.12 to 2.6.16 without
changing the kernel config file, but I am not sure if it's a good idea then
to make such big changes in such minor version steppings.

But you might have your reasons, and might even be able to explain them, or
have a versioning scheme ruleset. Is there something like that?

Henning

Re: xen versioning scheme

[Henning Sprang]

Sorry for double-posting this mail - I realized that I sent the mail from
the wrong address, resent it from the correct one, but at the same time the
first post seems to have been passed through by a moderator...

apologies,
Henning