From: "Denys Dmytriyenko" <denis@denix.org>
To: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] Couple questions about Dunfell
Date: Fri, 1 May 2020 14:07:44 -0400 [thread overview]
Message-ID: <20200501180744.GZ11927@denix.org> (raw)
In-Reply-To: <20200501132838.GA13726@kudzu.us>
On Fri, May 01, 2020 at 09:28:39AM -0400, Jon Mason wrote:
> On Wed, Apr 29, 2020 at 11:31:57AM +0200, Nicolas Dechesne wrote:
> > hi,
> >
> > On Sun, Apr 26, 2020 at 12:57 AM Denys Dmytriyenko <denis@denix.org> wrote:
> >
> > > Hi, Jon,
> > >
> > > I had couple questions:
> > >
> > > 1. What is the time frame for branching off Dunfell?
>
> TL;DR: Mid-May
>
> We have a chicken-egg problem with the Gem5 support and Python2.
> We've been doing all of our testing (until recently) on zeus. This is
> because we wanted to make sure any issues we encountered were ours and
> not an upstream issue. For dunfell, the current Gem5 support has a
> requirement for meta-python2. To add this to our internal git repos
> and test infrastructure would be painful. However, the upcoming
> release for Gem5 removes such a dependency. This release is scheduled
> for May 15th. So, we can either go through a bunch of work that will
> be thrown away or wait a couple extra weeks. We chose the latter.
>
> As a stop gap, we are using the beta version of the new Gem5 release
> to make sure everything is in working order and we should be able to
> cut a release very quickly once it is out.
>
> > > 2. What is the policy for backporting to Dunfell?
> >
> > I am definitely interested in these questions, or rather in the answers to
> > these questions! Since dunfell is LTS, I would expect a dunfell branch to
> > be maintained in meta-arm.
>
> The dunfell branch is planned to be a stable branch. Only bug fixes,
> no features. If an exception is to be made (which I really, really
> don't want to do), then it would be predicated on getting the relevant
> parts into the master branch of meta-arm.
Thanks for the details!
> > > I've got several patches in the pipeline that I'm testing and wanted to
> > > know
> > > my options.
>
> More than what you've already pushed?
Yeah, few more. Mostly fixes and cleanups for toolchain and gcc.
> Thanks,
> Jon
>
> > >
> > > Thanks.
> > >
> > > --
> > > Denys
> > >
> > >
>
> >
>
>
next prev parent reply other threads:[~2020-05-01 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 22:57 Couple questions about Dunfell Denys Dmytriyenko
2020-04-29 9:31 ` [meta-arm] " Nicolas Dechesne
2020-05-01 13:28 ` Jon Mason
2020-05-01 18:07 ` Denys Dmytriyenko [this message]
2020-05-04 20:12 ` Daniel D?az
2020-05-05 7:24 ` Bertrand Marquis
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=20200501180744.GZ11927@denix.org \
--to=denis@denix.org \
--cc=meta-arm@lists.yoctoproject.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 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.