All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Khalid Aziz <khalid@gonehiking.org>
Cc: Dave Young <dyoung@redhat.com>, Simon Horman <horms@verge.net.au>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	WANG Chao <chaowang@redhat.com>
Subject: Re: More frequent kexec-tools releases
Date: Wed, 29 Jan 2014 11:52:45 -0500	[thread overview]
Message-ID: <20140129165245.GD15077@redhat.com> (raw)
In-Reply-To: <1391013993.19367.22.camel@rhapsody>

On Wed, Jan 29, 2014 at 09:46:33AM -0700, Khalid Aziz wrote:
> On Tue, 2014-01-28 at 13:40 -0500, Vivek Goyal wrote:
> > I am wondering if there is any interest in more frequent releases of
> > kexec-tools. Say every 3 months or every 6 months.
> 
> Yes, that will be good. I maintain the kexec-tools package for Debian
> and I often find myself backporting fixes from git into Debian package
> as users find bugs that are already fixed in upstream. Being able to
> update the entire package to new release with all accumulated bugfixes
> periodically will be helpful.

Agreed. If we have more frequent releases of kexec-tools, then
distributions can easily rebase to newer releases more frequently and
that will reduce the overhead of cherry-picking and backporting fixes.

Also it allows distribution users to test new features sooner. For example,
kexec support on EFI systems. In worst case, a distribution user will have
to wait for an year or more before a release happens and user can test this
feature. And this is true for any feature which is introduced in kexec-tools.

Thanks
Vivek

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

      reply	other threads:[~2014-01-29 16:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 18:40 More frequent kexec-tools releases Vivek Goyal
2014-01-29  1:36 ` Zhang Yanfei
2014-01-29 14:23   ` Vivek Goyal
2014-01-31  5:23     ` Simon Horman
2014-01-31 14:30       ` Vivek Goyal
2014-02-04  8:31         ` Simon Horman
2014-02-04 12:41           ` Simon Horman
2014-02-04 14:31             ` Vivek Goyal
2014-02-05  1:12             ` Zhang Yanfei
2014-02-05  6:49               ` Simon Horman
2014-02-05 13:20                 ` Vivek Goyal
2014-02-06  1:55                   ` Simon Horman
2014-02-06 14:23                     ` Vivek Goyal
2014-02-06 23:58                       ` Simon Horman
2014-02-07  2:20                         ` Dave Young
2014-02-07 14:34                         ` Vivek Goyal
2014-02-12  1:16                           ` Simon Horman
2014-02-25  4:12                         ` WANG Chao
2014-01-29 16:46 ` Khalid Aziz
2014-01-29 16:52   ` Vivek Goyal [this message]

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=20140129165245.GD15077@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=chaowang@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=khalid@gonehiking.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.