From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Kilian Zinnecker <kilian.zinnecker@mail.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/1] configs/rock5b: Add patches to fix gcc12 warnings
Date: Sun, 20 Aug 2023 21:59:21 +0200 [thread overview]
Message-ID: <20230820195921.GS1778688@scaer> (raw)
In-Reply-To: <10326829.nUPlyArG6x@kilian-aisec>
Killian, All,
On 2023-08-20 21:42 +0200, Kilian Zinnecker via buildroot spake thusly:
> Thanks as well. I don't yet fully understand how the git branches in open
> source projects work, i.e., what exactly gets into the "next" branch (i.e.,
> how the next branch is actually defined) and what gets a release candidate "rc"
> tag. However, I just wanted to add that imho this patch then should also get
> into the next rc for 2023.08, because else the freshly introduced Rock 5B
> support in 2023.08 will be broken.
I guess every project has their own branch management.
In Buildroot, we have a three-month release cycle. The first two months,
there' only master which gets commits. The third month, master only get
fixes, and the 'next' branch gets new features. About every week in the
third month, we tag an rc release on master, and eventually we tag the
release. Then next is merged in to master, and we start a new cycle.
It may happen that, after an rc is tagged on master, we merge it into
next, so that next also gets critical fixes from master. We don;t do it
very often, though...
And now that I wrote the above, I remember we should have something the
manual... Yes, we do:
https://buildroot.org/downloads/manual/manual.html#RELENG
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-20 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 19:04 [Buildroot] [PATCH v3 0/1] Fix Rock 5B build, broken by gcc 12 warnings Kilian Zinnecker via buildroot
2023-08-20 19:04 ` [Buildroot] [PATCH v3 1/1] configs/rock5b: Add patches to fix gcc12 warnings Kilian Zinnecker via buildroot
2023-08-20 19:29 ` Yann E. MORIN
2023-08-20 19:42 ` Kilian Zinnecker via buildroot
2023-08-20 19:59 ` Yann E. MORIN [this message]
2023-08-20 20:55 ` Kilian Zinnecker via buildroot
2023-08-20 21:09 ` Kilian Zinnecker via buildroot
2023-08-20 21:29 ` Yann E. MORIN
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=20230820195921.GS1778688@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.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