From: Denys Dmytriyenko <denys@ti.com>
To: "Bode, Michael (PED-DEAS)" <Michael.Bode@bshg.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Will there be a yocto jethro branch in future?
Date: Wed, 17 Feb 2016 16:05:15 -0500 [thread overview]
Message-ID: <20160217210515.GG31480@edge> (raw)
In-Reply-To: <5f4fac1f4ae841ad99a481f1ef201f1d@MCHSWIEXMB5A.bsh.corp.bshg.com>
On Wed, Feb 17, 2016 at 09:19:30AM +0000, Bode, Michael (PED-DEAS) wrote:
> Hello,
>
> probably i'm not the first asking this question but i could'nt find any statement.
> I'm working with meta-ti embedded into yocto environment a lot. Really a great stuff.
> From time to time I update the layers according to the yocto releases. So I started from "dora" and shifted to "fido".
> Now I like to update also to "jethro".
> Question: "How is the policy of meta-ti integration regarding yocto releases?" Will there be a "jethro" branch as soon as the layer is compatible or can I assume that as long as there is no "jethro" branch the meta-ti layer is compatible to yocto head?
> If there will be a "jethro" branch, is there a time schedule for this?
As you can see, we skipped dizzy and jethro releases, as we don't have
resources to maintain 2 releases per year. I try to keep master up to date and
we plan to intersect the next 2.1 release in April, for which we'll have a new
branch in meta-ti.
--
Denys
prev parent reply other threads:[~2016-02-17 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 9:19 Will there be a yocto jethro branch in future? Bode, Michael (PED-DEAS)
2016-02-17 21:05 ` Denys Dmytriyenko [this message]
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=20160217210515.GG31480@edge \
--to=denys@ti.com \
--cc=Michael.Bode@bshg.com \
--cc=meta-ti@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.