Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Tony Jones <tonyj@suse.com>, Olaf Hering <ohering@suse.de>,
	kexec@lists.infradead.org, Jan Beulich <JBeulich@suse.com>
Subject: Re: Next kexec release
Date: Tue, 4 Feb 2014 11:19:08 -0500	[thread overview]
Message-ID: <20140204161908.GB8373@redhat.com> (raw)
In-Reply-To: <CAB=NE6WzCjtsq0hCUt=H62V7y2wd3dTeE-q0=R282kdobbXjcA@mail.gmail.com>

On Mon, Feb 03, 2014 at 07:49:11PM -0800, Luis R. Rodriguez wrote:
> Hey folks, I see recent discussions about desire for a new recent
> release of kexec, one of such reasons is kexec support on EFI systems.
> SUSE is also interested in this, and it'd be great if we can all synch
> up on supporting the same recent release.
> 

Hi Luis,

I wanted to make sure that there are more frequent releases of kexec-tools
so that every release of Fedora, we can rebase to new kexec-tools and
support that. 

I think this should should to Suse and other distributions. More frequent
releases will allow more frequent rebases to newer versions and allow
users to test newer kexec-tools easily.

Thanks to Simon that he has agreed to release kexec-tools every alternate
kernel release (roughly every 6 months).

W.r.t syncing on supporting same kexec-tools release, I am not sure how
will that work. Every distribution will have its own release schedule.
And most likely they will rebease to newer version when window for
next release opens so that it can get maximum testing time.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-02-04 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04  3:49 Next kexec release Luis R. Rodriguez
2014-02-04 16:19 ` Vivek Goyal [this message]
2014-02-04 16:39   ` Tony Jones

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=20140204161908.GB8373@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=JBeulich@suse.com \
    --cc=kexec@lists.infradead.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=ohering@suse.de \
    --cc=tonyj@suse.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