public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: Stable branch releases?
Date: Mon, 09 Feb 2009 13:39:20 -0600	[thread overview]
Message-ID: <49908668.1070909@us.ibm.com> (raw)
In-Reply-To: <49908557.7050504@redhat.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>> Hi Avi,
>>
>> Since a number of people are using the maint/2.6.29 branch, perhaps 
>> we could start doing releases from it?  For instance, a kvm-74.1, 
>> kvm-74.2, etc. set of releases.  Likewise, when we start 
>> maint/2.6.30, a new set of stable releases could follow.
>
> Yes, I want to do that.

Ok, is there anything standing in the way of doing this?  What would 
prevent us from doing a stable release in the next few days even?  Is 
there anything we can do to help?

>   One question is what to call these releases, though.

I'd like to see it be named kvm-XX.y or something like that to keep a 
close association between what the base release was.  For instance, you 
wouldn't expect HPET support in kvm-74.3 but you may expect it if it 
were kvm-stable-3 or something.

> I'd like to keep the kernel part synced with 2.6.x.y for as long as 
> that's maintained.

How do you deal with maint/2.6.29 right now in the kvm.git tree?  Do you 
sync that with the 2.6.x.y releases?

> Perhaps we can call these releases kvm-stable-x.y (though it would 
> cause confusion with kvm-xx).

If you're just suggesting introducing -stable, it really doesn't matter 
to me.  I don't think it's necessary FWIW.

>   So, users of kvm-stable-x.y would be running the same code as users 
> running Linux-2.6.x.y with the bundled kvm modules.

I think the majority of utility in the release numbers are associated 
with the userspace bits (maybe I'm a bit bias :-)).  I don't think most 
users care about the differences between 2.6.28 and 2.6.29 kernel bits, 
but the different between kvm-74 and kvm-83 is very important feature wise.

Regards,

Anthony Liguori

  reply	other threads:[~2009-02-09 19:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 19:26 Stable branch releases? Anthony Liguori
2009-02-09 19:34 ` Avi Kivity
2009-02-09 19:39   ` Anthony Liguori [this message]
2009-02-09 19:49     ` Glauber Costa
2009-02-09 20:10       ` Avi Kivity
2009-02-09 20:44         ` Anthony Liguori
2009-02-11 12:10           ` Avi Kivity
2009-02-11 13:13             ` Anthony Liguori
2009-02-11 13:18               ` Avi Kivity
2009-03-09 10:35           ` Avi Kivity
2009-03-09 13:52             ` Anthony Liguori
2009-03-09 14:39               ` Avi Kivity
2009-03-09 15:56                 ` Anthony Liguori
2009-02-09 20:07     ` Avi Kivity

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=49908668.1070909@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    /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