Re: GRUB 2.06 release

[Daniel Kiper]

On Mon, Dec 14, 2020 at 01:39:12PM +0100, Daniel Kiper wrote:
> On Wed, Jul 29, 2020 at 07:46:43PM +0200, Daniel Kiper wrote:
> > On Fri, May 29, 2020 at 02:07:29PM +0200, Daniel Kiper wrote:
> > > On Wed, Apr 22, 2020 at 12:24:40PM +0200, Daniel Kiper wrote:
> > > > On Mon, Mar 16, 2020 at 05:41:29PM +0100, Daniel Kiper wrote:
> > > > > On Wed, Mar 11, 2020 at 11:47:35AM +0100, Daniel Kiper wrote:
> > > > > > On Tue, Mar 03, 2020 at 06:26:03PM +0100, Daniel Kiper wrote:
> > > > > > > On Wed, Feb 19, 2020 at 04:01:38PM +0100, Daniel Kiper wrote:
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > As I told during my FOSDEM 2020 presentation we are preparing 
> > > > > > > > for
> > > > > > > > GRUB 2.06 release. Tentative schedule is below:
> > > > > > > >   - code freeze: 15th of March, 23:59:59 UTC; everything posted 
> > > > > > > > after
> > > > > > > >     that date will not be considered as a release material,
> > > > > > >
> > > > > > > Just a kind reminder... Less than two weeks left...
> > > > > >
> > > > > > Less than a week left... This is final call...
> > > > >
> > > > > Freeze in force! No new features are accepted at this point!
> > > > >
> > > > > I will be reviewing all patches posted before the end of Sunday. All 
> > > > > of
> > > > > them will be considered for inclusion in the release. Additionally, 
> > > > > all
> > > > > features under active development and discussed on grub-devel still 
> > > > > can
> > > > > be considered for inclusion. However, if there is a substantial danger
> > > > > of destabilizing the code or delaying the release I may reject any 
> > > > > patch
> > > > > at any point.
> > > > >
> > > > > I am especially interested in fixes and cleanups at this point...
> > > > >
> > > > > I am going to cut an RC in 2-4 weeks.
> > > >
> > > > Bad news is that we have delays... :-( Good news is that everything is 
> > > > going
> > > > forward... :-) I merged next portion of patches yesterday. I am working
> > > > on some fixes for issues which I found. I am also trying to work out
> > > > the best solution for other bugs which are lingering here and there. So,
> > > > please be patient... However, if you have any questions or suggestions
> > > > just drop me a line...
> > >
> > > Unfortunately there are still delays due to some unexpected things
> > > happening... Though I am still ploughing through backlog. I have
> > > recently posted a few fixes and cleanups required for rc1. Sadly there
> > > are still a few issues which have to be fixed. I am working on them. So,
> > > I hope that in the following weeks we will be able to cut rc1...
> > >
> > > If you are waiting for my review please bear with me. I will get back to
> > > you as soon as I can. Though I am mostly looking at important fixes in
> > > first order right now.
> >
> > I think this link [1] will explain my long absence... Sorry about that.
> >
> > I am going to go back to GRUB work next week. I will triage all the patches
> > and take all (obvious) fixes. Then I will release rc1 ASAP... All new 
> > features
> > will be taken after 2.06 release.
> >
> > Daniel
> >
> > [1] https://lists.gnu.org/archive/html/grub-devel/2020-07/msg00034.html
>
> Huh... This took longer than I wanted to. Anyway, I am going to cut
> 2.06-rc1 by the of this week. So, this is the final call to say what is
> missing in current master. I am going to take only critical code fixes
> after RC. Documentation, tests, etc. changes still will be welcome.

I merged all the patches which are needed for 2.06-rc1. However,
I discovered an issue in build of messages for translation. I have
to fix it before rc1 cut. I am going to do it at the beginning of
next year. Though I think you can start testing because code changes
are not expected at this point...

Daniel