From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1B1C3C433E0 for ; Thu, 9 Jul 2020 15:27:33 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D7545207D0 for ; Thu, 9 Jul 2020 15:27:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="X69onLAF" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D7545207D0 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:45642 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jtYSS-0001D3-5E for qemu-devel@archiver.kernel.org; Thu, 09 Jul 2020 11:27:32 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46746) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jtYRe-0008Ey-0g for qemu-devel@nongnu.org; Thu, 09 Jul 2020 11:26:42 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:34698 helo=us-smtp-delivery-1.mimecast.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1jtYRc-0002Ep-8v for qemu-devel@nongnu.org; Thu, 09 Jul 2020 11:26:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1594308399; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oHzCcHLoEeM1HdWOUAl3dACq6/T5JLGytFiyfBg/XS0=; b=X69onLAF9RPY8R1DlDkf10nBXL8VwGmcqBd4OoipOelNAcHQ7O6/9YTv2mu0tdSm84QLYL nsRRkSAerwkE8JHI3wEWJey7AaNTDAgYY5b/kKwdZjgpjfLBtSNNrSzn06OrVHjWvSxzRB rDl0KKlH8jUWVfHc2439QvEx6YYZm6c= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-265-OEU2T0bRNrOZDB7kyMV7Xw-1; Thu, 09 Jul 2020 11:26:37 -0400 X-MC-Unique: OEU2T0bRNrOZDB7kyMV7Xw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2053B102C80E; Thu, 9 Jul 2020 15:26:36 +0000 (UTC) Received: from redhat.com (unknown [10.36.110.45]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D7AF8724A0; Thu, 9 Jul 2020 15:26:33 +0000 (UTC) Date: Thu, 9 Jul 2020 16:26:30 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Thomas Huth Subject: Re: Is VXHS actually maintained? Message-ID: <20200709152630.GW3753300@redhat.com> References: <2666aec2-9872-6af6-7705-d7ce553f611c@redhat.com> MIME-Version: 1.0 In-Reply-To: <2666aec2-9872-6af6-7705-d7ce553f611c@redhat.com> User-Agent: Mutt/1.14.3 (2020-06-14) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Disposition: inline Received-SPF: pass client-ip=207.211.31.81; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-1.mimecast.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/07/09 11:02:51 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -30 X-Spam_score: -3.1 X-Spam_bar: --- X-Spam_report: (-3.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Cc: Kevin Wolf , Jeff Cody , QEMU , Max Reitz , =?utf-8?Q?Marc-Andr=C3=A9?= Lureau , ashmit602@gmail.com Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" 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 :|