From: Bob Cochran <yocto@mindchasers.com>
To: Zhenhua Luo <zhenhua.luo@freescale.com>,
Software Development Power Arch Multicore
<MCSWDEV@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto branches policy for concurrent SDK releases
Date: Thu, 09 Jan 2014 15:24:41 -0500 [thread overview]
Message-ID: <52CF0589.4040905@mindchasers.com> (raw)
In-Reply-To: <CA452391058F6D4E9715FB2C29D9312A0181242A@039-SN2MPN1-021.039d.mgd.msft.net>
On 11/22/2013 05:43 AM, Zhenhua Luo wrote:
> Hi all,
>
> Currently concurrent SDKs are on-going(e.g. SDK 1.5, T1040/T2080, LS1, etc), the same Yocto branch is used for multiple releases, there is conflict of Yocto recipes for different SDKs.
>
> To resolve above issue, following branch mechanism will be used:
>
> 1. For those layers without conflict(poky, meta-oe, meta-virtualization and layers reused from community), same branch will be used and no extra branches need to be created, change for those layer should be upstreamed synchronously.
>
> 2. For those layers with conflict, the branch specific to SDK are created, currently meta-fsl-ppc and meta-fsl-networking have conflict for different SDKs. Following branches will co-exist for such layers.
> a. Yocto release branch: dylan, dora. the common changes for all SDKs should be submitted against this branch and cherry-picked to SDK specific branches. The changes should be upstreamed synchronously.
> b. SDK specific branch: dylan-sdk1.5, dylan-t1_t2, etc. The SDK specific change should be submitted against SDK branch, when SDK is formally released, the changes will be upstreamed.
Hi Zhenhua,
Any plans to create a repo for meta-fsl-networking on git.yoctoproject
for Power / QorIQ developers?
It would be good for yocto users, such as myself, to be able to build
something incremental between the SDK releases using updated / patched
recipes pulled from the yocto repos, which should include
meta-fsl-networking.
Say I wanted to propose a patch to a recipe like fsl-image-full, which
is in meta-fsl-networking, how would I go about it?
Last February (2013), you proposed an FSL Yocto layers reorg that merged
layerscape/ARM with Power for QorIQ. I imagine you're getting close to
having something internally. Can you please share the vision with us
along with whether it will be public on the yocto project (as opposed to
kept under wraps with incremental SDK releases)?
Thank you,
Bob
>
> Please let me know if any comment.
>
>
> Best Regards,
>
> Zhenhua
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2014-01-09 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 10:43 Yocto branches policy for concurrent SDK releases Zhenhua Luo
2014-01-09 20:24 ` Bob Cochran [this message]
[not found] ` <1.9.2014-mgd.freescale.com-31-6352487069445086783412-5862@freescale.com>
2014-01-23 5:39 ` [mcswdev] " zhenhua.luo
[not found] <11.22.2013-mgd.freescale.com-31-6352068864395453777460-5604@freescale.com>
2013-11-22 13:32 ` Zhenhua Luo
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=52CF0589.4040905@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=MCSWDEV@freescale.com \
--cc=yocto@yoctoproject.org \
--cc=zhenhua.luo@freescale.com \
/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.