Re: IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup

From: Petr Vorel <petr.vorel@gmail.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: Patrick Steinhardt <ps@pks.im>, Dmitry <reagentoo@gmail.com>,
	The development of GNU GRUB <grub-devel@gnu.org>,
	Vladimir Serbinenko <phcoder@gmail.com>
Subject: Re: IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup
Date: Tue, 26 Jan 2021 20:57:50 +0100	[thread overview]
Message-ID: <20210126195750.GA2623@pevik> (raw)
In-Reply-To: <20210126130011.wfxrmb45yrfdx54m@tomti.i.net-space.pl>

> On Thu, Jan 21, 2021 at 10:30:11PM +0100, Petr Vorel wrote:
> > Hi Daniel,

> > [Cc Vladimir]
> > ...
> > > > > I don't really know about the release cycle, but personally I wouldn't
> > > > > mind to accelerate it. That's only my two cents though as somebody who
> > > > > hasn't been involved in the project that deeply.
> > > > +1 (that would allow to greatly reduce number of patches in distros, but
> > > > understand the lack of maintainers time).

> > > I hope we will be able to release 2.06 in 2-3 months. Now I am looking
> > > at cutting rc1 shortly. Expect it in the following weeks.
> > That'd be great.

> > > Definitely I do not want to make current release cycle a norm. I am
> > > going to work on improving it after 2.06 release. I think we will be
> > > targeting something between 6-12 months.
> > Anything than current situation will be great.
> > One would say that releasing more often with smaller diff would be better even
> > for you as a maintainer, but maybe the amount work to test everything before the
> > release is huge (given that testing e.g. Adrian does are probably done manually).

> > Busy projects with enough maintainers and other community members which helps
> > with reviewing and with working CI and good test coverage release every 3-4
> > months. It's clear that Grub isn't in that state, I wonder what could the
> > community do to help you to improve the situation a bit.

> At this point we need help with testing and reviews. We want to be sure
> as much as possible that current code is in pretty good state and ready
> for release. WRT reviews, if you can see something on the list which is
> in the area of your expertise do not hesitate to review/comment. If you
> are not sure the maintainers will be OK with your comment just say that.
> We can add our comments later. These really help us to improve GRUB code.
Thanks for info!

> I am also working on getting more time for GRUB maintainer work. I hope
> I will manage to do that soon and will be able to clear current backlog
> quickly.
Good luck!

> Daniel

Kind regards,
Petr