From mboxrd@z Thu Jan  1 00:00:00 1970
From: Miquel Raynal <miquel.raynal@bootlin.com>
Date: Tue, 13 Nov 2018 11:33:26 +0100
Subject: [U-Boot] [ANN] U-Boot v2018.11 delayed a day
In-Reply-To: <1f09ec2c-d2e6-0e83-541b-5e43fc736f41@gmail.com>
References: <20181112214016.GS11247@bill-the-cat>
 <8668e5b6-00a7-0ebb-8910-b9dd8dabf81b@gmail.com>
 <20181112222515.GU11247@bill-the-cat>
 <64cad1b6-99d6-f692-4b9f-aced8fd86fb5@gmail.com>
 <20181113011247.GV11247@bill-the-cat>
 <1f09ec2c-d2e6-0e83-541b-5e43fc736f41@gmail.com>
Message-ID: <20181113113326.1a328b0b@xps13>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: u-boot@lists.denx.de

Hi Marek,

+Jagan

Marek Vasut <marek.vasut@gmail.com> wrote on Tue, 13 Nov 2018 03:12:49
+0100:

> On 11/13/2018 02:12 AM, Tom Rini wrote:
> > On Tue, Nov 13, 2018 at 01:03:41AM +0100, Marek Vasut wrote: =20
> >> On 11/12/2018 11:25 PM, Tom Rini wrote: =20
> >>> On Mon, Nov 12, 2018 at 11:13:29PM +0100, Marek Vasut wrote: =20
> >>>> On 11/12/2018 10:40 PM, Tom Rini wrote: =20
> >>>>> Hey all,
> >>>>>
> >>>>> Since Jagan promise a v2 SPI PR for some build fixes that we should=
 have
> >>>>> in the release and I believe didn't get them out before the end of =
his
> >>>>> day, I'm letting everyone know now to expect the release tomorrow
> >>>>> instead, thanks! =20
> >>>>
> >>>> Will anyone have any chance to test those fixes to verify they didn't
> >>>> break anything ? =20
> >>>
> >>> Since they're obvious enough by inspection, I'm not worried about it.=
 =20
> >>
> >> Which patches are those ? =20
> >=20
> > The ones in question? =20
>=20
> Yes, is there a list ?

I think this is the branch:
https://github.com/openedev/u-boot-amarula/commits/v2-WIP5

And the successful Travis builds:
https://travis-ci.org/openedev/u-boot-amarula/builds/453885472

>=20
> >>>> I believe this is yet another manifestation of the problems of the 2
> >>>> month release cycle, which I think is too short and stressful. =20
> >>>
> >>> And I believe that's a red herring.  All the same I am still consider=
ing
> >>> changes. =20
> >>
> >> I'd really like to know how do other maintainers feel about this 2 mon=
th
> >> release cycle vs. for example 3 month like Linux does. I think the lat=
er
> >> is about right, 2 months is too short. =20
> >=20
> > Yes, I've asked before and there's a few people in the same camp as you,
> > and there's a few people who like 2 months, and there's a large number
> > of no strong opinions.  That's why I'm still thinking about changing
> > things again. =20
>=20
> Maybe we need a poll ?

I do agree on this.


Thanks,
Miqu=C3=A8l