public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
To: jes@trained-monkey.org, Jes Sorensen <jes.sorensen@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: release plan for mdadm
Date: Mon, 1 Mar 2021 13:22:44 +0100	[thread overview]
Message-ID: <e7d61078-bfb9-fd39-ba26-75e3a8c325a4@linux.intel.com> (raw)
In-Reply-To: <de867ab3-9942-77a0-c14d-dbfc67465888@linux.intel.com>

On 27.01.2021 12:39, 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.
> 
> What are your thoughts?
> Regards,
> Mariusz

Hi Jes,
Any feedback?

Mariusz

  reply	other threads:[~2021-03-01 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 11:39 release plan for mdadm Tkaczyk, Mariusz
2021-03-01 12:22 ` Tkaczyk, Mariusz [this message]
2021-03-02 22:50 ` Jes Sorensen
2021-03-03  8:13   ` Tkaczyk, Mariusz
2021-03-05 12:04     ` Radtke, Jakub
2021-03-10 15:02     ` Jes Sorensen
2021-03-03 16:52   ` Piergiorgio Sartor
2021-03-14 19:06   ` Felix Lechner

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=e7d61078-bfb9-fd39-ba26-75e3a8c325a4@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=jes.sorensen@gmail.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox