All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Jeff Cody" <codyprime@gmail.com>, QEMU <qemu-devel@nongnu.org>,
	"Max Reitz" <mreitz@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	ashmit602@gmail.com
Subject: Re: Is VXHS actually maintained?
Date: Thu, 9 Jul 2020 16:26:30 +0100	[thread overview]
Message-ID: <20200709152630.GW3753300@redhat.com> (raw)
In-Reply-To: <2666aec2-9872-6af6-7705-d7ce553f611c@redhat.com>

On Thu, Jul 09, 2020 at 05:20:58PM +0200, Thomas Huth wrote:
> On 09/07/2020 17.10, Marc-André Lureau wrote:
> > Hi,
> > 
> > VXHS block device was added ~3y ago in commit da92c3ff60b (block/vxhs.c:
> > Add support for a new block device type called "vxhs"), but it doesn't
> > compile anymore, at least since v5.0 (I haven't checked earlier).
> > 
> > The upstream repository (https://github.com/VeritasHyperScale/libqnio)
> > hasn't received any update since then.
> > 
> > What should we do about it?
> 
> IMHO: Mark it as deprecated in docs/system/deprecated.rst, then remove
> it in two releases if nobody shows up to maintain it.

If it doesn't even compile, do we even need to go through the full
deprecation cycle ? I tend to feel like the release where it first
fails to compile automatically starts the deprecation countdown.
So depending on when it first bit-rotted, we could be justified in
deleting it right away.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2020-07-09 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 15:10 Is VXHS actually maintained? Marc-André Lureau
2020-07-09 15:20 ` Thomas Huth
2020-07-09 15:25   ` Philippe Mathieu-Daudé
2020-07-09 15:26   ` Daniel P. Berrangé [this message]
2020-07-09 15:30     ` Peter Maydell
2020-07-09 15:41       ` Marc-André Lureau
2020-07-09 15:47         ` Peter Maydell
2020-07-09 15:50         ` Alex Bennée
2020-07-09 15:51           ` Peter Maydell
2020-07-09 16:02             ` Marc-André Lureau
2020-07-09 16:25             ` Alex Bennée

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=20200709152630.GW3753300@redhat.com \
    --to=berrange@redhat.com \
    --cc=ashmit602@gmail.com \
    --cc=codyprime@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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 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.