All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-Custodians] [ANN] U-Boot v2019.07-rc4 released
Date: Sat, 22 Jun 2019 17:08:51 +0200	[thread overview]
Message-ID: <6e0e35bc-d244-a428-1b32-86a41a7ba9fe@denx.de> (raw)
In-Reply-To: <CAPnjgZ3FThdMtePphq67WF1FoPbOAFkvSgEiRQdVRBW954U2Yw@mail.gmail.com>

On 6/22/19 4:55 PM, Simon Glass wrote:
> Hi Tom,
> 
> On Tue, 11 Jun 2019 at 02:33, Tom Rini <trini@konsulko.com> wrote:
>>
>> Hey all,
>>
>> It's release day and here is v2019.07-rc4.   At this point, I know we
>> have some regression fixes for i.MX that are coming, and I'm expecting a
>> fix to the build time failure for tinker-rk3288.
>>
>> To repeat myself about DM migration deadlines, first, let me say again,
>> that DM is not required for SPL.  This comes up enough that I want to
>> say it again here.  Next, if there is active progress on converting
>> things, we'll keep from pulling the code out.  This is why for example,
>> we haven't yet pulled out a lot of deprecated SPI code.  Some of it is
>> still in progress on being converted, so I need to update the series I
>> posted after the last -rc to remove still less drivers.
>>
>> In terms of a changelog,
>> git log --merges v2019.07-rc3..v2019.07-rc4
>> continues to improve in quality.  If you're sending me a PR, please
>> include a few lines or words in summary and I'll be sure to put it into
>> the merge commit.
>>
>> As I mentioned with -rc3, with this cycle is coming closer to an end,
>> it's time to decide if we're going to keep this 3 month cycle or go back
>> to 2 months.  After the last release while I did get some feedback, the
>> overall balance is still in the 3 month bucket.
> 
> I vote for 2 months. I find the current release disappears into a
> black hole for a about a month, and patches sit on the list for what
> seems like eternity. I have the option of doing a -next branch but it
> seems that very few do this.
> 
> I'd like to better understand the benefits of the 3-month timeline.

Stability, with the 2 months cycle, there was no time to stabilize the
release and fix bugs, everyone was just cannonfodding patches upstream
all the time. The result was always a release which wasn't quite well
done, had rough edges, unfixed bugs and it wasn't something which you
could deploy.

Now we have 1 month window where we only accept bugfixes and where
things slow down. This removes some stress from the maintainers too.
And that lets us take a step back and think about the bigger project
questions, rather than just dealing with the onslaught of patches.

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2019-06-22 15:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  1:31 [U-Boot] [ANN] U-Boot v2019.07-rc4 released Tom Rini
2019-06-11  2:56 ` [U-Boot] [U-Boot-Board-Maintainers] " Marek Vasut
2019-06-11 11:15   ` Tom Rini
2019-06-11 13:39     ` Marek Vasut
2019-06-11  5:38 ` Lukasz Majewski
2019-06-16 17:36 ` [U-Boot] Poplar broken in U-Boot v2019.07-rc4 Andreas Färber
2019-06-17  2:16   ` Shawn Guo
2019-06-17  2:19     ` Bin Meng
2019-06-17  2:31       ` Shawn Guo
2019-06-22 14:55 ` [U-Boot] [ANN] U-Boot v2019.07-rc4 released Simon Glass
2019-06-22 15:08   ` Marek Vasut [this message]
2019-06-22 15:10   ` [U-Boot] [U-Boot-Board-Maintainers] " Andreas Färber
2019-06-22 18:15     ` Simon Glass
2019-06-22 19:08       ` Andreas Färber
2019-06-22 19:14         ` Simon Glass
2019-06-22 19:49           ` Andreas Färber
2019-06-24 13:56             ` Simon Glass
2019-06-24 17:10               ` [U-Boot] [U-Boot-Custodians] " Marek Vasut
2019-06-25  0:10                 ` Simon Glass
2019-06-22 19:12       ` Heinrich Schuchardt
2019-06-22 19:43         ` Marek Vasut
2019-06-24 15:29           ` Tom Rini
2019-06-25 11:10             ` [U-Boot] [U-Boot-Board-Maintainers] [U-Boot-Custodians] " Neil Armstrong
2019-06-25 12:04               ` Tom Rini
2019-06-30 10:34                 ` Matwey V. Kornilov
2019-07-01  7:23                   ` Neil Armstrong
2019-07-02 16:04           ` [U-Boot] [U-Boot-Custodians] [U-Boot-Board-Maintainers] " Troy Benjegerdes
2019-07-02 17:03             ` Marek Vasut
2019-07-03 15:59             ` Simon Glass
2019-07-03 16:04               ` [U-Boot] [U-Boot-Board-Maintainers] [U-Boot-Custodians] " Tom Rini
2019-07-03 16:22                 ` Troy Benjegerdes
2019-07-03 19:34                   ` Heinrich Schuchardt
2019-06-25  3:51         ` [U-Boot] [U-Boot-Custodians] [U-Boot-Board-Maintainers] " Heiko Schocher
2019-06-30 10:32         ` Matwey V. Kornilov

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=6e0e35bc-d244-a428-1b32-86a41a7ba9fe@denx.de \
    --to=marex@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.