From: Miquel Raynal <miquel.raynal@bootlin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2018.11 delayed a day
Date: Tue, 13 Nov 2018 11:33:26 +0100 [thread overview]
Message-ID: <20181113113326.1a328b0b@xps13> (raw)
In-Reply-To: <1f09ec2c-d2e6-0e83-541b-5e43fc736f41@gmail.com>
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:
> >> On 11/12/2018 11:25 PM, Tom Rini wrote:
> >>> On Mon, Nov 12, 2018 at 11:13:29PM +0100, Marek Vasut wrote:
> >>>> On 11/12/2018 10:40 PM, Tom Rini wrote:
> >>>>> 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!
> >>>>
> >>>> Will anyone have any chance to test those fixes to verify they didn't
> >>>> break anything ?
> >>>
> >>> Since they're obvious enough by inspection, I'm not worried about it.
> >>
> >> Which patches are those ?
> >
> > The ones in question?
>
> 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
>
> >>>> I believe this is yet another manifestation of the problems of the 2
> >>>> month release cycle, which I think is too short and stressful.
> >>>
> >>> And I believe that's a red herring. All the same I am still considering
> >>> changes.
> >>
> >> I'd really like to know how do other maintainers feel about this 2 month
> >> release cycle vs. for example 3 month like Linux does. I think the later
> >> is about right, 2 months is too short.
> >
> > 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.
>
> Maybe we need a poll ?
I do agree on this.
Thanks,
Miquèl
next prev parent reply other threads:[~2018-11-13 10:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 21:40 [U-Boot] [ANN] U-Boot v2018.11 delayed a day Tom Rini
2018-11-12 22:13 ` Marek Vasut
2018-11-12 22:25 ` Tom Rini
2018-11-13 0:03 ` Marek Vasut
2018-11-13 1:12 ` Tom Rini
2018-11-13 2:12 ` Marek Vasut
2018-11-13 10:33 ` Miquel Raynal [this message]
2018-11-13 10:41 ` Marek Vasut
2018-11-13 10:54 ` Boris Brezillon
2018-11-13 11:02 ` Marek Vasut
2018-11-13 11:15 ` Jagan Teki
2018-11-13 11:23 ` Marek Vasut
2018-11-13 11:32 ` Jagan Teki
2018-11-13 15:57 ` Wolfgang Denk
2018-11-13 16:06 ` Jagan Teki
2018-11-14 9:23 ` Wolfgang Denk
2018-11-14 9:50 ` Jagan Teki
2018-11-14 9:47 ` Boris Brezillon
2018-11-14 10:21 ` Wolfgang Denk
2018-11-13 13:30 ` Philipp Tomsich
2018-11-13 11:01 ` Stefano Babic
2018-11-14 11:32 ` Anatolij Gustschin
2018-11-14 11:40 ` Stefan Roese
2018-11-14 12:21 ` Tom Rini
2018-11-14 11:54 ` Marek Vasut
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=20181113113326.1a328b0b@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=u-boot@lists.denx.de \
/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