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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 BDD78C433DB for ; Fri, 5 Mar 2021 12:05:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6CF5964FE2 for ; Fri, 5 Mar 2021 12:05:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229815AbhCEMEc (ORCPT ); Fri, 5 Mar 2021 07:04:32 -0500 Received: from mga03.intel.com ([134.134.136.65]:59383 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229591AbhCEME3 (ORCPT ); Fri, 5 Mar 2021 07:04:29 -0500 IronPort-SDR: pIjJ8zGWwHK45Ru8NOSBzBK3MuDF8qPD8nN52SF2VrgflUtuZTxs0RO01nROMvQt2u/pmSc5+t cE/xlTKM0rCA== X-IronPort-AV: E=McAfee;i="6000,8403,9913"; a="187690769" X-IronPort-AV: E=Sophos;i="5.81,224,1610438400"; d="scan'208";a="187690769" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Mar 2021 04:04:28 -0800 IronPort-SDR: VL88Zl3xQ8LW4f7h5SQjo7FHx6tm3cJ1e91u4BRn3N5itCUTP85lS/g0U3eLi1pSE+awOp0GJ4 yrlHJlQcRLPg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,224,1610438400"; d="scan'208";a="370169598" Received: from linux.intel.com ([10.54.29.200]) by orsmga006.jf.intel.com with ESMTP; 05 Mar 2021 04:04:28 -0800 Received: from [10.213.1.144] (jradtke-MOBL1.ger.corp.intel.com [10.213.1.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id 4AF6B580224; Fri, 5 Mar 2021 04:04:27 -0800 (PST) Subject: Re: release plan for mdadm To: Jes Sorensen Cc: linux-raid@vger.kernel.org References: <2cb77cb7-468d-88ed-a938-63b35e574177@trained-monkey.org> From: "Radtke, Jakub" Message-ID: <31736f90-9dd4-6174-3476-5ade8beb68d0@linux.intel.com> Date: Fri, 5 Mar 2021 13:04:24 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: pl Precedence: bulk List-ID: X-Mailing-List: linux-raid@vger.kernel.org Hi Jes,     I have also resent the patches related to the bitmap support in IMSM posted some time ago. Regards, Jakub > On 02.03.2021 23:50, Jes Sorensen wrote: >> On 1/27/21 6:39 AM, Tkaczyk, Mariusz wrote: >>> Hi Jes, >>> >>> It's been a while since last mdadm release. Mdadm-4.2 release that was >>> mentioned back in July does not happened yet. It's getting messy to >>> manage mdadm across multiple distributions. >>> >>> Also, not all OSVs are willing to cherry-pick the patches, especially >>> for stable project - like mdadm, so only critical bugfixes are landing >>> in the distros. >>> As a result - new OSes has various forks of mdadm-4.1 and the >>> difference >>> is growing with every backported patch. It leads us to situation where >>> those forks may have own bugs, caused by many missing bugfixes or >>> wrongly >>> resolved merge conflicts. >>> To be honest - it becomes more and more problematic for us to track all >>> fixes in different supported distros. >>> >>> We are searching for solutions for those problems and we are >>> counting on >>> your support: >>> Short term - is there any way that we can help you to release next >>> version >>> of mdadm soon? >>> >>> Long term - what do you think about smaller, more frequent releases of >>> mdadm? Maybe twice a year is an option (similar to RedHat/Ubuntu >>> schedule)? That would be better for us and for vendors. They will need >>> to follow upstream instead resolving bugs reported by us or community. >>> >>> The benefits will be gained by everyone. User will get up-to-date >>> software much faster, with minimal vendor input and modifications. >>> Mdadm bugs will be predictable across distros. We could help with >>> testing IMSM and basic functionality of native metadata. >> >> Hi Mariusz, >> >> Sorry for the slow response. Our daughter was born in late December and >> I was on paternity leave through Feb 5, so still catching up. I also >> switched teams at work back in July so my focus was shifted. > Hi Jes, > Congratulations:) >> >> I'd very much like to see a release, and we should do one quick. Doing >> more regular releases will also make it easier to ship them, so I am not >> against that at all. >> >> I am not aware of anything major pending right now, so if we can get >> focus on any pending patches and get them in over the next week or two, >> then I can cut an -rc and we can do a release soon. Especially if you >> can help out regression testing the -rc candidate(s). >> >> Cheers, >> Jes >> > Thanks for answer. Please review all patches in queue, and mark -rc. > Then I will schedule regression. > > Mariusz