grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GRUB release schedule?


From: Josef Bacik
Subject: Re: GRUB release schedule?
Date: Fri, 21 Aug 2015 10:57:55 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

On 08/21/2015 10:30 AM, Konrad Rzeszutek Wilk wrote:
On Fri, Aug 21, 2015 at 10:18:08AM -0700, Josef Bacik wrote:
On 08/21/2015 10:11 AM, Konrad Rzeszutek Wilk wrote:
On Fri, Aug 21, 2015 at 09:56:59AM -0700, Josef Bacik wrote:
On 07/20/2015 11:22 AM, Peter Jones wrote:
Hi everyone,
Is there a plan for when upcoming GNU GRUB releases will happen?

As far as I can tell, the last official release on
ftp://ftp.gnu.org/gnu/grub/ was 2.00 on 28-Jun-2012, and the last beta
on http://alpha.gnu.org/pub/gnu/grub/ for the next version was
2.02~beta2 on 24-Dec-2013 .  There are (give or take) 471 patches
committed since that beta 18 months ago.

In the mean time, nearly every Linux distro is shipping a package
derived from the 2.02~beta2 release plus some number of patches,
some from the upstream repo and some not, and it's cumbersome to rectify
which ones aren't upstream vs which ones have been fixed upstream with
/nearly/ the same patch, etc., with all the noise of so many patches
since the release.

I suspect this would be better for a lot of GRUB users if releases
happened on a regular schedule, or if, relatively often (say once or
twice per year), a release schedule that spans several weeks and
organized some kind of alpha->beta->release progression were decided
upon and followed.

So, can we make a release process that happens according to some regular
cadence?  What needs to be done to make regular releases happen?  Going
for years with the patch volume GRUB sees without doing a release is
really not good for anybody.


I'd like to +1 this.  I think the tests are important for sure, but there's
no reason we can't set a release cadence and at least cut an -rc1 and spend
some time fixing up the test failures.  Facebook is going to be using grub2
in our provisioning environment, we would like to have official builds
rather than running from git.  Thanks,

What is the tests that are needed? Surely as different distros we could
pool some hardware together to make this work?


There was just some mention of tests failing earlier in the thread, that's
what I was talking about.

Right.

What do GRUB maintainers think are the top tests that are needed and
on what architectures? And do you have any ideas on how to automate it?

We're automating testing internally by provisioning the different types of
boxes we have with grub2.  Once I have the ipv6 and tcp window scaling stuff
in I plan to have continuous testing on grub2 to make sure our use case
doesn't get broken by somebody.  Thanks,

Fantastic! Would there by any way to get this reflector copied on the emails
on the testing?

Yeah, Facebook is not interested in carrying internal patches on open source patches for long periods of time (obviously we'll carry stuff to fix our problem right now while we work out getting it fixed upstream). Whenever anything breaks there will be a loud screaming noise coming from my corner of the world followed by emails to everybody who's to blame. Thanks,

Josef




reply via email to

[Prev in Thread] Current Thread [Next in Thread]