From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests
Date: Fri, 18 Nov 2022 18:09:51 +0200 [thread overview]
Message-ID: <Y3euT9EKWqACmd8q@nuoska> (raw)
In-Reply-To: <e7158cb97e3f8112e94296ad64df8ebf7792b995.camel@linuxfoundation.org>
Hi,
On Fri, Nov 18, 2022 at 04:04:01PM +0000, Richard Purdie wrote:
> On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote:
> > Additionally I'm currently interested in kirkstone LTS branch so would like
> > any changes to be there too...
>
> The idea is that we develop things in master, then they become
> available in the next LTS release, not the previous one.
>
> People somehow seem to think that we add development patches to master
> and immediately backport them to the last LTS. This is not how
> development or the LTS is meant to work :(.
>
> We've not going to be forced into poor interface/API choices just
> because people want things backported to the current LTS.
>
> This is why I'm so worried about the lack of planning and development
> happening on master, people need to be thinking and planning ahead. To
> be clear, this isn't just about this issue but a pattern we're seeing
> far more widely.
Agreed, I'm trying to get into working closer to master but not there
yet...
Cheers,
-Mikko
next prev parent reply other threads:[~2022-11-18 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 7:12 [PATCH 0/2] image specific configuration with oeqa runtime tests Mikko Rapeli
2022-11-17 7:12 ` [PATCH 1/2] oeqa: add utils/data.py with get_data() function Mikko Rapeli
2022-11-17 7:12 ` [PATCH 2/2] oeqa parselogs.py: use get_data() to fetch image specific error list Mikko Rapeli
2022-11-17 14:22 ` [OE-core] [PATCH 0/2] image specific configuration with oeqa runtime tests Alexandre Belloni
2022-11-17 14:28 ` Mikko Rapeli
2022-11-17 15:17 ` Richard Purdie
2022-11-17 15:39 ` Mikko Rapeli
2022-11-17 16:57 ` Richard Purdie
2022-11-18 14:32 ` Mikko Rapeli
2022-11-18 15:04 ` Richard Purdie
2022-11-18 15:57 ` Mikko Rapeli
2022-11-18 16:04 ` Richard Purdie
2022-11-18 16:09 ` Mikko Rapeli [this message]
2022-11-18 16:11 ` Richard Purdie
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=Y3euT9EKWqACmd8q@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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